Add ability to configure the prefix of the label keys #51
Conversation
This file contains hidden or 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
acrylic-style
approved these changes
Feb 4, 2025
Member
acrylic-style
left a comment
acrylic-style
left a comment
There was a problem hiding this comment.
Sorry for the delay - the code looks good to me, merging tomorrow!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds the ability to configure the prefix used by label keys. This is done via
label-key-prefixin the config or theKUVEL_LABEL_KEY_PREFIXenvironment variable. (Default is the originalkuvel.azisaba.net)This is useful when you want to have the same servers be used in different proxies with different names.