adding the ability to change the default podManagementPolicy for StatefulSets #823

Merged
maximilien merged 1 commit from bodaciousbiscuits/garage:main into main 2024-05-25 18:35:54 +00:00
Contributor

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.

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.
bodaciousbiscuits added 1 commit 2024-05-20 02:33:33 +00:00
adding the ability to change the default podManagementPolicy for StatefulSets
All checks were successful
ci/woodpecker/pr/debug Pipeline was successful
39b37833c5
Author
Contributor
[API Reference](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#pod-management-policies)
bodaciousbiscuits changed title from WIP: adding the ability to change the default podManagementPolicy for StatefulSets to adding the ability to change the default podManagementPolicy for StatefulSets 2024-05-21 14:49:52 +00:00
maximilien approved these changes 2024-05-25 18:32:50 +00:00
Owner

This effectively allow for the operator to tell the scheduler to terminate all pods at once instead of doing a stagged roll out.

This effectively allow for the operator to tell the scheduler to terminate all pods at once instead of doing a stagged roll out.
Owner

We might want to add updateStrategy one day if people want to terminate/update their pod manually

We might want to add `updateStrategy` one day if people want to terminate/update their pod manually
maximilien merged commit d38509ef4b into main 2024-05-25 18:35:54 +00:00
Sign in to join this conversation.
No description provided.