-
Notifications
You must be signed in to change notification settings - Fork 7k
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
fix(tiller): correctly sort PodDisruptionBudget objects before pods that might use them #4769
Conversation
9894722
to
3dd9588
Compare
…hat might use them Signed-off-by: Matt Tucker <ultimateboy@gmail.com>
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.
LGTM
It turns out, the error I was really running into was caused by an upstream bug: kubernetes/kubernetes#63757 that was fixed in k8s 1.12.0 Basically, the The only way to work around this is to delete the PodDisruptionBudget object before you do a helm upgrade.... or update to k8s 1.12.0. I still think this pull request is useful, but it turns out not to be the real solution. |
…hat might use them (helm#4769) Signed-off-by: Matt Tucker <ultimateboy@gmail.com> Signed-off-by: Sebastien Plisson <sebastien.plisson@gmail.com>
…hat might use them (helm#4769) Signed-off-by: Matt Tucker <ultimateboy@gmail.com> Signed-off-by: Sebastien Plisson <sebastien.plisson@gmail.com>
…hat might use them (helm#4769) Signed-off-by: Matt Tucker <ultimateboy@gmail.com>
…hat might use them (helm#4769) Signed-off-by: Matt Tucker <ultimateboy@gmail.com>
Without this, using a pod disruption budget causes errors like this: