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
operator, k8s: Prevent CEC watcher goroutine leak #24316
Conversation
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you provide justification as to why this change is needed? It's not clear how there is a goroutine leak. The K8s watchers will always be running forever until Cilium shuts down, so moving to a context here doesn't seem to have any impact.
I refer to this #21913 |
Can you check it against this comment? |
ok,I thought it was all |
/test-1.25-4.19 |
For testing, its probably good to ensure everything shuts down correctly. Edit: just saw the comment you linked Anyway, would be worth documenting the reasoning for the change in the commit. |
Changes make sense to me. |
I have no other comment :) |
@yulng Were you going to work on this one some more, or should it be closed? If you are still interested in it, it needs:
|
Christarazi's comment only talks about test/controlplane ,but i searched all and modified it |
@yulng I think if you change your commit message to include some information about how this will affect mainly the tests, as in the comment linked above, then rebase, we should be good to go. |
ok,done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you update the commit msg title to:
operator, k8s: Prevent CEC watcher goroutine leak
It's ok |
Use the ctx passed to instead of wait.NeverStop for prevent goroutine leakage. Signed-off-by: yulng <wei.yang@daocloud.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix and the PR!
For future submissions, we ask for justification upfront so that we can understand why you are submitting a change. This way, we can review and validate the fix with ease. For bugfixes, this is especially important, along with how you were able to find the issue.
/test |
net-next failed to start, let's give it another try ... |
/test-1.26-net-next |
happy CI, happy me |
Thanks everyone |
fix:prevent goroutine leakage