Skip to content

Demo: workload placed only on an at-limit NodePool — DO NOT MERGE - #23

Closed
pvishwa3 wants to merge 1 commit into
mainfrom
pr/karpenter-at-limit-rule
Closed

pvishwa3 wants to merge 1 commit into
mainfrom
pr/karpenter-at-limit-rule

Conversation

@pvishwa3

@pvishwa3 pvishwa3 commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Same change as #21. On deployment-risk-action 1.0.17 the PR gate should block it with HIGH wrs-addon-karpenter-placement-fits-only-pools-at-limit, because rtzkd-capped has limits cpu 0 and 0 nodes. #21 passed at LOW 18 on 1.0.16. Do not merge.

… placement-fits-only-pools-at-limit) — DO NOT MERGE
@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown

Deployment risk: HIGH (score 61) — 4 findings

Severity Rule Resource Title
LOW mrs-diff-nodeselector-narrowed Deployment/rtz-gate-demo/gate-web nodeSelector narrowed
LOW mrs-diff-nodeselector-tightened Deployment/rtz-gate-demo/gate-web nodeSelector added or tightened

Capacity fit (1)

  • Not known Deployment rtz-gate-demo/gate-web at 2 replica(s) (spec.replicas) on the cluster's last sync 6d1a9b02-16ee-4311-875c-c765e8935830: where its pods go is not known: no new node the pools may add takes any of the 2 pods left without a home (2 no node matches its placement); rtzkd-capped: it has no node that takes pods now, so what it would add is not known.

If a zone is lost (each on its own, this PR's workloads placed on what is left):

  • us-east-1b: not known (rtz-gate-demo/gate-web) · the zone's pods back in ~8 min
  • us-east-1f: not known (rtz-gate-demo/gate-web) · the zone's pods back in ~8 min · 1 not back on their own

Add-on findings · Karpenter (1)

Severity Rule Resource Title
HIGH wrs-addon-karpenter-placement-fits-only-pools-at-limit Deployment/rtz-gate-demo/gate-web Every Karpenter NodePool this workload fits is at its limits
What changed and how to fix it
  • mrs-diff-nodeselector-narrowed · Deployment/rtz-gate-demo/gate-web — Deployment rtz-gate-demo/gate-web nodeSelector was narrowed ({} → {karpenter.sh/nodepool=rtzkd-capped,}). A tighter nodeSelector reduces the pool of nodes replicas can land on, increasing single-node concentration risk. Confirm enough distinct nodes still match.
    Fix: A Deployment/StatefulSet's nodeSelector was narrowed (a key was added or changed). A tighter nodeSelector reduces the pool of nodes replicas can land on, increasing single-node concentration risk. Confirm enough distinct nodes still match.
  • mrs-diff-nodeselector-tightened · Deployment/rtz-gate-demo/gate-web — Deployment rtz-gate-demo/gate-web nodeSelector was added/tightened ({} → {karpenter.sh/nodepool=rtzkd-capped,}). Fewer nodes may satisfy the new constraint; verify at least one live node carries the required label(s).
    Fix: A workload's nodeSelector had a key added or changed. Fewer nodes may satisfy the new constraint. Confirm at least one live node carries the required label(s).
  • wrs-addon-karpenter-placement-fits-only-pools-at-limit · Deployment/rtz-gate-demo/gate-web — Deployment rtz-gate-demo/gate-web: Its placement fits only NodePool rtzkd-capped (cpu 0 of 0) — at its limits, with no node running; every other NodePool is ruled out. Karpenter launches no node for a NodePool at its limits, so these pods stay Pending. Raise the pool's spec.limits in this change, or place the workload on a NodePool with room.
    Fix: The NodePools the workload's Karpenter placement fits have reached spec.limits and run no node, so Karpenter launches none for its pods. Raise the pool's limits or place the workload on a NodePool with room.

Cluster-aware checks: on — 55 runtimez lookup(s) answered.

@pvishwa3

pvishwa3 commented Nov 8, 2026

Copy link
Copy Markdown
Contributor Author

Demo finished (Karpenter gate verified live) — closing, never meant to merge.

@pvishwa3 pvishwa3 closed this Nov 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant