SingleDisruptionMode [api_object]ai-synthesized · conf 0.82
SingleDisruptionMode specifies that children can be disrupted independently.
scheduling
Represents the maximum number of pods that can be disrupted at one time.
Why it matters Ensures that a certain number of pods are not simultaneously affected by disruptions, such as node failures or maintenance.
Key facts - Maximum number of pods to disrupt - Disruption mode for scheduling
Common pitfalls - Insufficient disruption mode can lead to cascading failures - Incorrectly set disruption mode can cause pod delays
Related Pod Disruptions, Scheduling Strategies
Sources
swagger.json — “io.k8s.api.scheduling.v1alpha3.SingleDisruptionMode”