kubectl-ko: trace using ovs-ovn instead of kube-ovn-cni #4471
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: zcq98 <[email protected]>
bobz965
approved these changes
Sep 4, 2024
liyh-yusur
pushed a commit
to liyh-yusur/kube-ovn
that referenced
this pull request
Sep 10, 2024
Signed-off-by: zcq98 <[email protected]> Signed-off-by: liyh <[email protected]>
bobz965
pushed a commit
that referenced
this pull request
Sep 11, 2024
Signed-off-by: zcq98 <[email protected]>
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.
Pull Request
What type of this PR
Examples of user facing changes:
Which issue(s) this PR fixes
We should use the ovs-ovn pod for
traceandtcpdumpbecause in some cases, thekube-ovn-cnipod might encounter issues, while theovs-ovnpod remains functional.