We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened:
PUB may unexpectedly interrupt Pod gc issued by KCM, which can lead Pod leak if KCM gc did not retry or retry many hours later.
What you expected to happen:
PUB webhooks never interrupt Pod gc.
How to reproduce it (as minimally and precisely as possible):
Delete workload let's say Sts or CloneSet, then Pod will be deleted by KCM gc later. Sometimes, Pod to delete will be leaking there for a lone time.
Anything else we need to know?:
The root cause is we return error when PUB CR is deleted in RetryOnConflict. Related codes is here,
kruise/pkg/control/pubcontrol/pub_control_utils.go
Line 105 in 8bb8964
The solution is simple, just check error type as we can , ignore it if it is NotFound error.
Environment:
kubectl version
The text was updated successfully, but these errors were encountered:
@Spground You are right, can you fix the bug?
Sorry, something went wrong.
zmberg
Successfully merging a pull request may close this issue.
What happened:
PUB may unexpectedly interrupt Pod gc issued by KCM, which can lead Pod leak if KCM gc did not retry or retry many hours later.
What you expected to happen:
PUB webhooks never interrupt Pod gc.
How to reproduce it (as minimally and precisely as possible):
Delete workload let's say Sts or CloneSet, then Pod will be deleted by KCM gc later. Sometimes, Pod to delete will be leaking there for a lone time.
Anything else we need to know?:
The root cause is we return error when PUB CR is deleted in RetryOnConflict. Related codes is here,
kruise/pkg/control/pubcontrol/pub_control_utils.go
Line 105 in 8bb8964
The solution is simple, just check error type as we can , ignore it if it is NotFound error.
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: