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
Implement rolling update for daemon sets #22543
Comments
#15310 covers requirements for DaemonSet to graduate from beta to GA, including server-side update orchestration. I'd rather put effort into that, but it's tricky, and we don't plan to work on that in 1.3. If you'd like to contribute a client-side solution, though that's not the long-term direction we have in mind (#12143), it shouldn't introduce a new command. Instead, we should make https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/cmd/rollingupdate.go Because For example:
Other than the command itself, I wouldn't expect the update procedure to share code, though. The current rolling-update command creates a new ReplicationController and gradually scales it up while scaling the old one down. In the case of In the case of DaemonSet, kubectl would do the opposite: it would update the original DaemonSet and delete pods one by one to cause them to be replaced. If cc @mikedanese @davidopp @madhusudancs @janetkuo @Kargakis @pwittrock @gmarek |
1.6 includes rolling upgrades for DaemonSets. |
Thanks for the update! 👍 |
Make sure SIGTERM shutdown the controller manager and scheduler API server Origin-commit: 04e4ee15ef6e8deccb91db65c5e12e25b0d71c04
Hi,
Sorry for doing it in the wrong order as mentioned here : https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md#contributing-a-patch
I did #22439 to address this problem (on kubectl side)
The need is to be able to update a daemon set in a single command line.
Basically it is equivalent to do :
EDIT : @bgrant0607 suggested to update the ds instead of delte / recreate
The text was updated successfully, but these errors were encountered: