fix: kube-ovn-cni always dump-flows br-provider per period #4969
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
but this node is in pn.Spec.ExcludeNodes, and then it will generate a lot of logs Signed-off-by: clyi <[email protected]>
dosubot
bot
added
size:XS
zhangzujian
approved these changes
Feb 7, 2025
changluyi
deleted the
fix_always_dump_br_provider_when_no_provider_on_the_node_1.12
branch
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.
but this node is in pn.Spec.ExcludeNodes, and then it will generate a lot of logs
Pull Request
What type of this PR
Examples of user facing changes:
Which issue(s) this PR fixes
Fixes #(issue-number)
underlay mode , when node is in the provider-network.Spec.ExcludeNodes, the kube-ovn-cni will generate lots of logs like below