-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Updating statefulset from v1beta1 to v1beta2 #56806
Comments
/sig api-machinery |
/sig apps |
/remove-sig api-machinery |
@ryanmcnamara |
@danielqsj At any rate it appears the default really is RollingUpdate, because my second test
Actually does roll the pod. It appears that
and
end up storing different objects in k8s, which doesn't make sense to me |
@ryanmcnamara
|
@ryanmcnamara
v1beta2:
|
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
I have a stateful set that I created with api version v1beta1, I'm trying to update it to add a new annotation in the pod template using the v1beta2 api version in the update request but the update does not roll the pod. It seems that updating pods of stateful sets only works if it was initially created at version v1beta2, which I believe is a bug.
See
https://gist.github.com/ryanmcnamara/55c1327754b9fbc4518f2334f4e184b0
I did
However (after deleting the statefulset)
kubectl version
):version:
The text was updated successfully, but these errors were encountered: