adding the ability to change the default podManagementPolicy for StatefulSets #823
No reviewers
Labels
No labels
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#823
Loading…
Reference in a new issue
No description provided.
Delete branch "bodaciousbiscuits/garage:main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Previously when using StatefulSets, the default management policy is set to OrderedReady, meaning if any node in the chain is down, the rest won't spin up. I know DaemonSets solve this problem, but it would be nice to have the option.
API Reference
WIP: adding the ability to change the default podManagementPolicy for StatefulSetsto adding the ability to change the default podManagementPolicy for StatefulSetsThis effectively allow for the operator to tell the scheduler to terminate all pods at once instead of doing a stagged roll out.
We might want to add
updateStrategy
one day if people want to terminate/update their pod manually