Skip to content

added types of podManagementPolicy #51511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: dev-1.34
Choose a base branch
from
+12 −0
Draft

added types of podManagementPolicy #51511

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions content/en/docs/concepts/workloads/controllers/statefulset.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,6 +363,18 @@ that are running with the `MaxUnavailableStatefulSet`
enabled.
{{< /note >}}

#### PodManagementPolicy
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Try a level 3 heading in sentence case.


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should (eventually) have a feature-state shortcode.

You can determine the order at which the pods are deleted by specifying the `.spec.PodManagementPolicy`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Early feedback

Suggested change
You can determine the order at which the pods are deleted by specifying the `.spec.PodManagementPolicy`
You can influence the order at which the pods are deleted,
using the `.spec.podManagementPolicy`

field. There are two policies that you can configure for each StatefulSet:

`parallel`
: When updating, there will always be maxUnavailable number of pods terminating except the last batch

`orderedReady`
: When updating, the number of pods terminating won't always be maxUnavailable, but sometimes less than
that. This implementation avoids out of order Terminations of pods.

### Forced rollback

When using [Rolling Updates](#rolling-updates) with the default
Expand Down