chore: set unique cluster label for each release #2803
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Wylie Hobbs <[email protected]>
hobbsh
requested review from
mapno,
swartz-k,
BitProcessor,
faustodavid,
dgzlopes,
unguiculus and
Whyeasy
as code owners
hobbsh
force-pushed
the
set-unique-cluster-label
branch
from
3e4db4f
to
0e928b6
Compare
4 tasks
|
Any news on this feature ? tks |
|
@hobbsh |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addressing this issue where Loki/Tempo ingesters can join each other's ring because
cluster_labelseems to be defaulted to something common to both components. This change should mitigate the issue in the future.