Repository navigation
Commit ac248de
committed
fix(kubernetes): stop the Proxmox CCM outliving the node it runs on
The chart tolerated every taint with a blanket `operator: Exists`, which reads
as "run anywhere" and does something else as well: it matches
node.kubernetes.io/unreachable:NoExecute, so the DefaultTolerationSeconds
admission plugin adds no 300s bound and the Pod is never evicted from a Node
that has died.
That turns a machine replacement into a deadlock, because the controller that
removes a departed Node is this one. The stale Node keeps the Pod, the Pod keeps
the controller off the live node, the new node keeps its uninitialized taint,
and recovery needs an operator to delete the Node by hand.
Tolerating only the uninitialized taint — which is all that was ever needed to
land on a fresh node — lets admission add the bounded NoExecute tolerations
back. Verified by deleting the Machine: the Pod moved to a live node on its own,
the departed Node was cleaned up without help, and the replacement reached
Running in about three minutes.
Signed-off-by: Marian Koreniuk <[email protected]>
Assisted-by: LLM1 parent 0f11a37 commit ac248de
1 file changed
Lines changed: 12 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
21 | 30 | | |
22 | | - | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
23 | 34 | | |
24 | 35 | | |
25 | 36 | | |
| |||
0 commit comments