Don't consider Crashloopbackoff pods as part of PDB #684
Labels
area/usability
Usability related
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
needs/planning
Needs (more) planning with other MCM maintainers
priority/1
Priority (lower number equals higher priority)
How to categorize this issue?
/area performance
/area robustness
/area usability
/kind enhancement
/priority 3
What would you like to be added:
Currently upstream treats Crashloopbackoff pods as
Unavailable
and so if a PDB is configured withmaxUnavailable=1
with 2 pods , 1 pod Pending and other Crashloopbackoff, then the pod eviction request is denied for such pod and node draining can't proceed.There is a discussion upstream to deal with this kubernetes/kubernetes#72320 and a PR to ignore Crashloopbackoff pods from PDB is raised kubernetes/kubernetes#105296
Testing is required after the PR gets merged and MCM starts using the corresponding k8s version
Why is this needed:
So that MCM draining is not stuck till drainTimeout for CrashLoopbackoff pods with PDB.
The text was updated successfully, but these errors were encountered: