This repository was archived by the owner on Mar 25, 2024. It is now read-only.
Upgrade metadata filter #37
Merged
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
Prior, was not using consraints for dependencies which causes install to use the latest packages. This can cause inconsistent builds at different times or on different machines despite using the same config. Fluent and metadata filter are being upgraded to match upstream and resolve pods restarting due to not handling closed connections properly.
paynejacob
approved these changes
Dec 21, 2020
nickgerace
approved these changes
Dec 21, 2020
cbron
approved these changes
Dec 23, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem:
Pods are restarting due to watch connections closing.
Update:
Update metadata filter to version that has logic to gracefully handle closed connections. This is the same fix as upstream:
fluent/fluentd-kubernetes-daemonset#495
Issue:
rancher/rancher#30425