[k8s] Juju controller and model operators should run with higher priority
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Harry Pidcock |
Bug Description
On some stress tests, the team noticed that modeloperator pod got evicted from a node that was having memory contention.
Although this behavior is expected in k8s, Juju should take provisions to not have its own control plane evicted and/or not scheduling due to lack of resources.
The recommendation is to create a PriorityClass with higher value and setting it to all juju control plane pods (controller, model-operators).
Documentation: https:/
That means:
1. These pods will have higher priority when k8s needs to decide which pods to evict from a given node
2. These pods get priority when (re)scheduling.
Changed in juju: | |
status: | New → Confirmed |
importance: | Undecided → High |
status: | Confirmed → Triaged |
milestone: | none → 2.9.45 |
assignee: | nobody → Harry Pidcock (hpidcock) |
Changed in juju: | |
milestone: | 2.9.45 → 2.9.46 |
I was working in another similar bug, and stumbled in this again. Another thing we were looking into is PodDisruptionBu dget: https:/ /kubernetes. io/docs/ tasks/run- application/ configure- pdb/
Reference bug: https:/ /github. com/canonical/ postgresql- k8s-operator/ issues/ 269