Skip to content

gate-web: move to Karpenter NodePool rtzkd-capped (post-deploy gate demo) - #21

Merged
pvishwa3 merged 2 commits into
mainfrom
pr/karpenter-capped-pool
Nov 7, 2026
Merged

pvishwa3 merged 2 commits into
mainfrom
pr/karpenter-capped-pool

Conversation

@pvishwa3

@pvishwa3 pvishwa3 commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Karpenter demo for the post-deploy gate. Meant to be merged.

  • nodeSelector: karpenter.sh/nodepool: rtzkd-capped. That NodePool exists but has limits.cpu: 0, so Karpenter refuses every launch.
  • The rollout uses maxUnavailable: 0, so the two old pods keep serving while the new ones stay Pending. Argo shows Progressing, then Degraded after progressDeadlineSeconds: 300.
  • Expected post-deploy verdict: FAIL, with Karpenter's reason attached (step 16: NodePool rtzkd-capped at its limit).
  • DEMO_RUN bumped so the change is a fresh rollout.

Needs the backend in RUNTIMEZ_URL to run eac with #603 / #604. The hosted app.runtimez.io is on 219c70c0 (11-03) and will judge it FAIL without the Karpenter line.

Undo after the run: revert this PR.

🤖 Generated with Claude Code

https://claude.ai/code/session_014NPEGf1kUYALnqg7HFRtBH

…emo)

rtzkd-capped has limits.cpu 0, so Karpenter refuses every launch; the new pods stay Pending and the rollout never completes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014NPEGf1kUYALnqg7HFRtBH
@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown

Deployment risk: LOW (score 18) — 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
MEDIUM wrs-nodeselector-vs-matching-nodes Deployment/gate-web Deployment/gate-web declares nodeSelector karpenter.sh/nodepool=rtzkd-capped — 0 of 3 nodes match

Capacity fit (1)

  • Not known Deployment rtz-gate-demo/gate-web at 2 replica(s) (spec.replicas) on the cluster's last sync 68115671-232a-4d09-8e65-eb802e1cbc32: 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
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-nodeselector-vs-matching-nodes · Deployment/gate-web — gate-web declares nodeSelector karpenter.sh/nodepool=rtzkd-capped — 0 of 3 live nodes in the cluster satisfy the constraint set. Pods will sit Pending indefinitely (FailedScheduling). This cluster has an autoscaler (Karpenter/cluster-autoscaler) installed — a matching node MAY be provisioned on demand, but no NodePool/Provisioner configuration guarantees the requested label(s)/taint tolerance. Confirm a pool provides them.

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

…hat refuses the launch

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014NPEGf1kUYALnqg7HFRtBH
@pvishwa3
pvishwa3 merged commit 8c86fdf into main Nov 7, 2026
1 check passed
pvishwa3 added a commit that referenced this pull request Nov 7, 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