-
Notifications
You must be signed in to change notification settings - Fork 797
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
pdb: default to maxUnavailable=1 instead of minAvailable=1 #2039
pdb: default to maxUnavailable=1 instead of minAvailable=1 #2039
Conversation
91530db
to
3df3da3
Compare
So if we have 2 replicas, it will still ensure there will at least be one available, right? |
Yepp! Note btw that maxUnavailable was introduced in k8s 1.9 or something, which was later than the PDBs were introduced in the first place in z2jh. |
Omg, |
a65be2f
to
ce72e8c
Compare
ce72e8c
to
f36ef45
Compare
Thanks, @consideRatio! |
jupyterhub/zero-to-jupyterhub-k8s#2039 Merge pull request #2039 from consideRatio/pr/pdb-max-unavailable
Thanks @yuvipanda for your help with review/merge! |
If you want to lower the replicas of user-scheduler to 1, then you will get the same PDB issues we have had with hub/proxy (#1938) where they block upgrades etc because we have
minAvailable: 1
instead ofmaxUnavailable: 1
in order to handle workloads.