argo-cd/resource_customizations/policy/PodDisruptionBudget/testdata/degraded.yaml
Andrii Korotkov a7ff791ba5
chore: Don't degrade PDB on InsufficientPods (#20171) (#20665)
Closes #20171

There are valid use cases for InsufficientPods, e.g. running some jobs or tests that don't want to be terminated. See the discussion on the issue for more details. So don't degrade the PDB on InsufficientPods condition.

This needs to be cherry picked to 2.13, as many people may not upgrade otherwise.

Signed-off-by: Andrii Korotkov <andrii.korotkov@verkada.com>
2024-11-07 09:09:52 -08:00

29 lines
652 B
YAML

apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
name: foo
namespace: bar
spec:
minAvailable: 3
selector:
matchLabels:
app.kubernetes.io/name: foo
status:
conditions:
- lastTransitionTime: "2024-09-06T18:29:05Z"
message: ""
observedGeneration: 2
reason: InsufficientPods
status: "False"
type: DisruptionAllowed
- lastTransitionTime: "2024-09-06T18:29:06Z"
message: ""
observedGeneration: 2
reason: SyncFailed
status: "False"
type: DisruptionAllowed
currentHealthy: 2
desiredHealthy: 3
disruptionsAllowed: 0
expectedPods: 2
observedGeneration: 2