-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Update K8s manifests with rolling upgrade for calico/node Daemonset #777
Comments
We should document how to do this, but I'm not entirely sure we want to enable the rolling-update in our checked-in manifests across the board - it should be a deliberate action on the users behalf to trigger this behavior. EDIT: Maybe we do want to enable it. Open to hearing arguments for it :) |
Let's do this in the next release. DaemonSet rolling-update support has been around long enough that I think it's safe, and is the desired behavior for most users. |
Closing in favor of #1272 |
Add a node selector to the calicoctl manifests.
With the rolling upgrade capability of Daemonsets in kubernetes 1.6 we can enable that in our manifests and change our Upgrade story for calico/node.
The text was updated successfully, but these errors were encountered: