kubernetes-sigs / karpenter / 29755130663

82%

main: 82%

Pull #3160

github

feat: treat explicit limits.nodes: 0 as a NodePool disable toggle

As a cluster operator I want to define a disabled NodePool that I may enable later.
The spec does not provide an explicit toggle so I use nodes limit of zero.

Currently Karpenter continuously logs "node limits have been exhausted" error.

Pre-filter NodePools with spec.limits.nodes == 0 out of scheduling instead of
retrying every pending pod against them and logging an error.
Also publish NoCapacity warning event on the NodePool so the disabled state is visible.

15 of 15 new or added lines in 2 files covered. (100.0%)

16584 of 20112 relevant lines covered (82.46%)

97847.52 hits per line