Enable full DNS names #266
Open
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: jakub-racek-swi <[email protected]>
|
|
Closed
|
Just leaving it here that I cannot merge the PR myself as I do not have write access 😄 |
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.
Description:
Expanding the field for the collection of DNS names and by extension workload names in metric labels. The names of workloads can get long, for example if there is a certain service running on a certain pod in a certain namespace all that information gets concatenated into this string. It was limited to 80 characters before, while 256 characters is the actual theoretical limit.
This branch was migrated from #260
Link to tracking Issue: #256
Testing: Manual testing, running in devbox
Documentation: none