Skip to content

SLM: StatefulSet rollouts respect Node lifecycle state #6265

Description

@rthallisey

Enhancement Description

StatefulSet rollouts can be blocked when a Pod in the set is unavailable because its Node is shutting down, unreachable, or undergoing maintenance. StatefulSets preserve stable Pod identity and ordered rollout
semantics. The controller cannot create a replacement Pod with the same identity while the old Pod still exists.

This means a single Pod stuck on a Node affected by lifecycle activity can halt rollout progress. Users and rollout tooling may only see that the StatefulSet is waiting for Pods to become ready, without knowing whether the blocker is caused by the new revision, storage attachment, scheduling, or intentional Node maintenance.

Node lifecycle conditions give the StatefulSet controller and users shared context for this blocked state. The condition MaintenanceInProgress can explain when a specific StatefulSet Pod is unavailable because the Node is being lifecycled.

The KEP will define how StatefulSet status reports Pods affected by Node lifecycle context.

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

Metadata

Metadata

Labels

sig/appsCategorizes an issue or PR as relevant to SIG Apps.sig/nodeCategorizes an issue or PR as relevant to SIG Node.wg/node-lifecycleCategorizes an issue or PR as relevant to WG Node Lifecycle.

Type

No type

Projects

Status
Needs Triage
Status
No status
Status
No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions