Skip to content

regress: 30 replicas x 2 CPU (expect capacity findings) — DO NOT MERGE - #27

Open
pvishwa3 wants to merge 1 commit into
mainfrom
pr/regress-oversized-replicas
Open

pvishwa3 wants to merge 1 commit into
mainfrom
pr/regress-oversized-replicas

Conversation

@pvishwa3

Copy link
Copy Markdown
Contributor

Gate regression: 30 replicas at 2 CPU / 4Gi each. Expected: capacity-fit findings.

🤖 Generated with Claude Code

…T MERGE

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Deployment risk: LOW (score 0) — 1 finding

Capacity fit (1)

  • Fits on new nodes Deployment rtz-gate-demo/gate-web at 30 replica(s) (spec.replicas) on the cluster's last sync 5d854760-8354-452f-891d-c2e43460e4e6: 22 of 30 pod(s) place only on a node an autoscaler may add (rtzk-healthy, unpooled); no ResourceQuota or LimitRange in namespace rtz-gate-demo constrains it; but mid-rollout 8 of its 29 surge pod(s) fit on today's nodes beside the old ones (with the other rollouts' surge pods, not the new workloads' pods or Pending ones); maxUnavailable 0 lets no old pod go first, so the rollout waits for a node an autoscaler adds — and stalls if none is added.

New nodes this needs: +8 × k3s (rtzk-healthy, on-demand), not priced: the nodes are not on AWS.

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

  • eu-west-1a: survives on new nodes (rtz-gate-demo/gate-web)

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

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