-
Notifications
You must be signed in to change notification settings - Fork 762
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
[BUG] cloneset reuse terminating pod's name when pvc exists #1099
Comments
|
@willise Yeah, this is the expected behavior for now. But I understand your intention, how about add a new optional strategy field in |
I think this works, but I have another concern about the old PVC. After the terminating pod is deleted finally, should the old PVC be deleted manually or be processed by cloneset? |
With the field enabled, cloneset should cleanup those useless PVCs and then create new Pods with new PVCs. |
Ok, I am looking forward it. |
And you are welcome if interested in contributing this :) |
What happened:
The node is not ready and pod with pvc on this node is evicted. But as the kubelet is unready so it doesn't really delete the pod and the pod stuck in terminating state.
cloneset try to scale out a new pod and it finds there is a pvc exsits, so it reuse the pod name referred by pvc to create the pod. But the terminating pod already exists then it fails.
What you expected to happen:
A new pod can be created successfully.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version):The text was updated successfully, but these errors were encountered: