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

Make daemonsets do a rolling update #570

Merged
merged 2 commits into from
Mar 13, 2018
Merged

Conversation

yuvipanda
Copy link
Collaborator

Without this, the continuous pre-puller pods do not work,
since they're stuck in the old image version forever.

https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/
has more info

Without this, the continuous pre-puller pods do not work,
since they're stuck in the old image version forever.

https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/
has more info
rollingUpdate:
# Arbitrarily large number, since we want all the old daemonsets to die immediately
# and new ones to be born
maxUnavailable: 1000
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Great catch, @consideRatio! fixed.

@consideRatio
Copy link
Member

Nice catch! I remember thinking it did not matter for the hook-image-puller and left it out at one point... Doh!

LGTM!

@minrk minrk merged commit e7a147d into jupyterhub:master Mar 13, 2018
@manics manics mentioned this pull request Aug 15, 2018
7 tasks
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.

3 participants