Skip to content

Commit 6c4e152

Browse files
authored
Merge pull request #48485 from johngmyers/patch-1
Clarify PDB maxUnavailable only works if all pods have same controller
2 parents c75d9b3 + ffb9e2d commit 6c4e152

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/docs/tasks/run-application/configure-pdb.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ for policy/v1 an empty selector matches every pod in the namespace.
124124

125125
You can specify only one of `maxUnavailable` and `minAvailable` in a single `PodDisruptionBudget`.
126126
`maxUnavailable` can only be used to control the eviction of pods
127-
that have an associated controller managing them. In the examples below, "desired replicas"
127+
that all have the same associated controller managing them. In the examples below, "desired replicas"
128128
is the `scale` of the controller managing the pods being selected by the
129129
`PodDisruptionBudget`.
130130

0 commit comments

Comments
 (0)