Skip to content
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

Merged
merged 1 commit into from
Oct 12, 2018

Conversation

ultimateboy
Copy link

@ultimateboy ultimateboy commented Oct 12, 2018

Without this, using a pod disruption budget causes errors like this:

"Upgrade \"<rel-name>\" failed: no PodDisruptionBudget with the name \"<pdb-name>\" found"

@ultimateboy ultimateboy force-pushed the sort-pdb branch 3 times, most recently from 9894722 to 3dd9588 Compare October 12, 2018 19:38
…hat might use them

Signed-off-by: Matt Tucker <ultimateboy@gmail.com>
Copy link
Member

@technosophos technosophos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@technosophos technosophos added this to the 2.11.1 - Bugfix milestone Oct 12, 2018
@technosophos technosophos merged commit 147c821 into helm:master Oct 12, 2018
@ultimateboy
Copy link
Author

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 DisruptedPods field cannot be null and if you are trying to edit your PodDisruptionBudget, but dont currently have any disrupted pods, then k8s will fail validation and your release will fail.

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.

splisson pushed a commit to splisson/helm that referenced this pull request Dec 6, 2018
…hat might use them (helm#4769)

Signed-off-by: Matt Tucker <ultimateboy@gmail.com>
Signed-off-by: Sebastien Plisson <sebastien.plisson@gmail.com>
splisson pushed a commit to splisson/helm that referenced this pull request Dec 6, 2018
…hat might use them (helm#4769)

Signed-off-by: Matt Tucker <ultimateboy@gmail.com>
Signed-off-by: Sebastien Plisson <sebastien.plisson@gmail.com>
splisson pushed a commit to splisson/helm that referenced this pull request Dec 6, 2018
…hat might use them (helm#4769)

Signed-off-by: Matt Tucker <ultimateboy@gmail.com>
splisson pushed a commit to splisson/helm that referenced this pull request Dec 6, 2018
…hat might use them (helm#4769)

Signed-off-by: Matt Tucker <ultimateboy@gmail.com>
dmitrytokarev added a commit to dmitrytokarev/helm that referenced this pull request Oct 9, 2019
…stallOrder.

Port helm#6266 helm#4769 helm#3899 to Helm 3.
Signed-off-by: Dmitry Tokarev <dm.tokarev@yahoo.com>
dmitrytokarev added a commit to dmitrytokarev/helm that referenced this pull request Oct 9, 2019
…stallOrder.

Port helm#6266 helm#4769 helm#3899 to Helm 3.
Signed-off-by: Dmitry Tokarev <dm.tokarev@yahoo.com>
dmitrytokarev added a commit to dmitrytokarev/helm that referenced this pull request Oct 9, 2019
…stallOrder.

Port helm#6266 helm#4769 helm#3899 to Helm 3.

Signed-off-by: Dmitry Tokarev <dm.tokarev@yahoo.com>
hickeyma pushed a commit that referenced this pull request Oct 10, 2019
…stallOrder. (#6624)

Port #6266 #4769 #3899 to Helm 3.

Signed-off-by: Dmitry Tokarev <dm.tokarev@yahoo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants