SLM: Maintenance-aware DaemonSet rollouts

[rthallisey]

Enhancement Description

During a DaemonSet rollout, a broken Node or a Node undergoing maintenance can remain unavailable for reasons unrelated to the new DaemonSet revision. That Node can consume the rollout's availability budget indefinitely, preventing or slowing the controller from progressing the rollout on healthy Nodes.

DaemonSet status reports aggregate availability but does not explain when Pods are unavailable because their Nodes are shutting down or undergoing maintenance. Users and rollout tooling therefore cannot distinguish a broken rollout from intentional Node lifecycle activity, which can produce misleading alerts and availability reporting.

The DaemonSet controller will use Node lifecycle conditions as context for rollout behavior and status. MaintenanceInProgress will inform rollout
progress and placement, while GracefulNodeShutdownInProgress and MaintenanceInProgress will provide lifecycle attribution in DaemonSet status. The KEP will describe rollout ordering and address availability accounting when nodes are affected by lifecycle states.

This KEP assumes that MaintenanceInProgress will be set externally.

• One-line enhancement description (can be used as a release note): Make DaemonSet rollouts and status aware of Node lifecycle state.
• Kubernetes Enhancement Proposal: TBD
• Discussion Link:
  • KEP-5683 user story: Broken Nodes Can Consume Rollout Budget
  • KEP-5683 user story: DaemonSet Rollouts Aren't Reporting the Node's State
  • kubernetes/kubernetes#138240
  • kubernetes/kubernetes#139226
• PRs by stage and milestone:
  • Alpha - TBD
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

/sig apps
/sig node
/wg node-lifecycle

[rthallisey]

/assign @ronaknnathani

[kubernetes-prow]

@rthallisey: GitHub didn't allow me to assign the following users: ronaknnathani.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign @ronaknnathani

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ronaknnathani]

@rthallisey commenting here so that the assignment goes through. I can take this up. :)

You might have to try /assign again.

[rthallisey]

/assign @ronaknnathani