Performance optimizations for kubernetes_metadata filter #71
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
kubernetes_metadata filter enriches messages with kubernetes context like pod_id, namespace_name, labels etc. It reads all pods from api server and subscribed for the updates. With relatively large clusters it generates enormous load on the api server as it list ALL pods for the whole cluster instead of just for the machine where agent is running. Issue is fixed by filter developers: fabric8io/fluent-plugin-kubernetes_metadata_filter#170 However this fix is not included into the image used by AWS. With this pull request I upgrade image version to latest with the filter plugin fix and pass K8S_NODE_NAME env variable which enables the optimization.
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 of changes:
kubernetes_metadata filter enriches messages with kubernetes context
like pod_id, namespace_name, labels etc. It reads all pods from api
server and subscribed for the updates. With relatively large clusters
it generates enormous load on the api server as it list ALL pods for the
whole cluster instead of just for the machine where agent is running.
Issue is fixed by filter developers:
fabric8io/fluent-plugin-kubernetes_metadata_filter#170
However this fix is not included into the image used by AWS.
With this pull request I upgrade image version to latest with the filter
plugin fix and pass K8S_NODE_NAME env variable which enables the
optimization.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.