adding the ability to change the default podManagementPolicy for StatefulSets #823
No reviewers
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
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