Skip to content
This repository has been archived by the owner on Jul 30, 2021. It is now read-only.

Daemonset objects should use rolling update strategy #518

Closed
aaronlevy opened this issue May 17, 2017 · 0 comments
Closed

Daemonset objects should use rolling update strategy #518

aaronlevy opened this issue May 17, 2017 · 0 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. low hanging fruit priority/P1

Comments

@aaronlevy
Copy link
Contributor

We should make use of daemonset rolling update functionality now that we're on v1.6:

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

The fields will need to be added to our manifests (the default is the existing behavior).
@aaronlevy aaronlevy added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. low hanging fruit priority/P1 labels May 17, 2017
@lblackstone lblackstone mentioned this issue May 24, 2017
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. low hanging fruit priority/P1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aaronlevy