Skip to content

Commit 71cdde7

Browse files
committed
content/en/docs/tasks/run-application/configure-pdb: Acceptable overlapping PDBs
The previous "must be careful not to create" wording was making folks uncomfortable about brief overlap periods while transitioning between two PDBs [1]. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1861104#c29
1 parent fc73f29 commit 71cdde7

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

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

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -236,9 +236,6 @@ You can use a PDB with pods controlled by another type of controller, by an
236236
- only an integer value can be used with `.spec.minAvailable`, not a percentage.
237237

238238
You can use a selector which selects a subset or superset of the pods belonging to a built-in
239-
controller. However, when there are multiple PDBs in a namespace, you must be careful not
240-
to create PDBs whose selectors overlap.
241-
242-
243-
244-
239+
controller. The eviction API will disallow eviction of any pod covered by multiple PDBs,
240+
so most users will want to avoid overlapping selectors. One reasonable use of overlapping
241+
PDBs is when pods are being transitioned from one PDB to another.

0 commit comments

Comments
 (0)