Metrics must listen on ipv4 and ipv6 #447
Open
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
Metrics must listen on ipv4 and ipv6 so that this helm chart will work in ipv6 enabled k8s clusters. This is a implementation of a work around found in this bug: fluent/fluentd#3001 Signed-off-by: Sjoerd Oostdijck <[email protected]>
stevehipwell
requested review from
patrick-stephens and
stevehipwell
as code owners
Contributor
|
Please can you rebase on the latest versions so we can bring in the updated CI? |
Author
|
Done |
Author
|
The checks fail because there is no |
Document notable changes and update metrics endpoint. Signed-off-by: Sjoerd Oostdijck <[email protected]>
Add CHANGELOG.md for Fluentd Helm Chart
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.
Metrics must listen on ipv4 and ipv6 so that this helm chart will work in ipv6 enabled k8s clusters.
This is a implementation of a work around found in this bug: fluent/fluentd#3001
Signed-off-by: Sjoerd Oostdijck [email protected]