-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cilium-dbg/troubleshoot: do not import cilium-dbg from operator #37326
Merged
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
aanm
added
release-note/misc
This PR makes changes that have no direct user impact.
needs-backport/1.16
This PR / issue needs backporting to the v1.16 branch
needs-backport/1.17
This PR / issue needs backporting to the v1.17 branch
labels
Jan 29, 2025
/test |
aanm
force-pushed
the
pr/fix-troubleshooting-concurrency
branch
from
January 29, 2025 09:49
8efa608
to
ece4894
Compare
/test |
giorio94
approved these changes
Jan 29, 2025
Since we are importing cilium-dbg from the operator, this is causing all of its init() functions to be initialized causing some potential concurrency issues as cilium-dbg is initializing functions assuming it's the only binary using them, same as with the operator. To avoid this problem, we will move the troubleshoot as an independent package that can be imported by the operator, the clustermesh-apiserver and the cilium-dbg tool. Fixes: 5f0e3e2 ("operator: add troubleshoot subcommands") Signed-off-by: André Martins <andre@cilium.io>
aanm
force-pushed
the
pr/fix-troubleshooting-concurrency
branch
from
January 29, 2025 11:05
ece4894
to
6625571
Compare
/test |
dlapcevic
approved these changes
Jan 29, 2025
asauber
approved these changes
Jan 29, 2025
maintainer-s-little-helper
bot
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Jan 29, 2025
giorio94
added
backport-pending/1.17
The backport for Cilium 1.17.x for this PR is in progress.
and removed
needs-backport/1.17
This PR / issue needs backporting to the v1.17 branch
labels
Jan 31, 2025
giorio94
added
backport-pending/1.16
The backport for Cilium 1.16.x for this PR is in progress.
and removed
needs-backport/1.16
This PR / issue needs backporting to the v1.16 branch
labels
Jan 31, 2025
github-actions
bot
added
backport-done/1.17
The backport for Cilium 1.17.x for this PR is done.
backport-done/1.16
The backport for Cilium 1.16.x for this PR is done.
and removed
backport-pending/1.17
The backport for Cilium 1.17.x for this PR is in progress.
backport-pending/1.16
The backport for Cilium 1.16.x for this PR is in progress.
labels
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-done/1.16
The backport for Cilium 1.16.x for this PR is done.
backport-done/1.17
The backport for Cilium 1.17.x for this PR is done.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/misc
This PR makes changes that have no direct user impact.
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.
Since we are importing cilium-dbg from the operator, this is causing all of its init() functions to be initialized causing some potential concurrency issues as cilium-dbg is initializing functions assuming it's the only binary using them, same as with the operator. To avoid this problem, we will move the troubleshoot as an independent package that can be imported by the operator, the clustermesh-apiserver and the cilium-dbg tool.
Fixes: 5f0e3e2 ("operator: add troubleshoot subcommands")