-
Notifications
You must be signed in to change notification settings - Fork 219
cleanup is only called on restart #1599
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
Comments
@metacosm Do you have a good idea, hope to get your help |
@qinzhichao01 are you using the newest version? |
yes,my pom version is 4.1.1 |
|
will take a look into it |
@qinzhichao01 added a PR, this will fix the issue. The problem was with something else, the generation filter, the pod does not seems to have Until released you can turn off generation aware processing: by setting this flag to false. That should fix you issue. |
@csviri good job, thanks for your solution |
see also on k8s slack: https://kubernetes.slack.com/archives/C0EG7JC6T/p1668518118307749 |
Uh oh!
There was an error while loading. Please reload this page.
I am going to use java-operator-sdk to implement my own operator, but I found that when I implemented the Cleaner method, I found that when deleting a pod, the cleanup method was not called, and the k8s pod would not be deleted, only in The cleanup method will be called after restarting the application, and the pod will be deleted. My implementation is as follows. Is my implementation wrong?
calll method
The text was updated successfully, but these errors were encountered: