-
Notifications
You must be signed in to change notification settings - Fork 42.1k
api: Allow MaxSurge to be set on DaemonSets during update #96375
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
api: Allow MaxSurge to be set on DaemonSets during update #96375
Conversation
|
/sig apps |
a76adaf to
045acb4
Compare
|
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
045acb4 to
b967931
Compare
|
/priority important-soon |
b967931 to
243562b
Compare
|
/assign @kubernetes/sig-apps-pr-reviews |
|
/triage accepted |
soltysh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
/retest Review the full test history for this PR. Silence the bot with an |
3 similar comments
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/approve |
|
/test all |
|
/test pull-kubernetes-e2e-gce-ubuntu-containerd |
|
/refresh |
|
/test pull-kubernetes-e2e-gce-100-performance |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: janetkuo, kow3ns, smarterclayton, soltysh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test all |
The MaxSurge field on DaemonSet rolling updates allows a daemonset workload to have two pods running simultaneously on a node during an update in order to perform zero-disruption handoffs of client traffic.
When the maxsurge daemonset gate is disabled, the registry and validation must properly handle stripping the field. In the special case where that would leave the MaxUnavailable field set to 0, we must set it to 1 which is the default value.
67a4871 to
c37c93f
Compare
|
/lgtm |
|
/retest |
|
/test pull-kubernetes-e2e-gce-ubuntu-containerd |
|
Implementation PR is ready for review in #96441 |
MaxSurge allows a daemonset workload to run multiple instances of the same pod on a node during rollout to minimize downtime of the daemonset to other consumers.
This PR adds the feature gate and API for kubernetes/enhancements#1591 and configures round tripping behavior when the gate is enabled or disabled as well as validation rules to prevent inconsistent values. Subsequent PRs will add implementation.
/kind feature
/kind api-change
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: