Skip to content

regress: weakened rollout (expect BLOCK) — DO NOT MERGE - #26

Open
pvishwa3 wants to merge 1 commit into
mainfrom
pr/regress-weaken-rollout
Open

pvishwa3 wants to merge 1 commit into
mainfrom
pr/regress-weaken-rollout

Conversation

@pvishwa3

Copy link
Copy Markdown
Contributor

Gate regression after the Cilium work: probes removed, memory limit 32Mi below the 64Mi request, NetworkPolicy deleted. Expected: PR gate fails at HIGH.

🤖 Generated with Claude Code

…y (expect BLOCK) — DO NOT MERGE

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

Copy link
Copy Markdown

Deployment risk: HIGH (score 61) — 5 findings

Severity Rule Resource Title
HIGH mrs-req-exceeds-limit-mem Deployment/gate-web Memory request exceeds limit — pod rejected at admission
HIGH mrs-diff-networkpolicy-removed NetworkPolicy/rtz-gate-demo/gate-web NetworkPolicy removed — isolation lost
MEDIUM mrs-diff-readiness-probe-removed Deployment/rtz-gate-demo/gate-web Readiness probe removed
MEDIUM mrs-diff-liveness-probe-removed Deployment/rtz-gate-demo/gate-web Liveness probe removed
MEDIUM mrs-diff-memory-limit-reduced Deployment/rtz-gate-demo/gate-web Memory limit reduced — OOMKill risk
What changed and how to fix it
  • mrs-req-exceeds-limit-mem · Deployment/gate-web — resources.requests.memory is greater than resources.limits.memory; the API server rejects this pod spec at admission and the workload will not schedule. Set requests.memory <= limits.memory.
  • mrs-diff-networkpolicy-removed · NetworkPolicy/rtz-gate-demo/gate-web — NetworkPolicy rtz-gate-demo/gate-web was removed. Pods previously isolated by it may now send/receive unrestricted traffic. Confirm the isolation is no longer needed.
    Fix: A NetworkPolicy was removed. Pods it previously isolated may now send or receive unrestricted traffic. Confirm the isolation is no longer required, or restore the policy.
  • mrs-diff-readiness-probe-removed · Deployment/rtz-gate-demo/gate-web — Deployment rtz-gate-demo/gate-web container 'web' had its readinessProbe removed. Unready pods will receive traffic during rollout, causing user-facing errors. Re-add the readiness probe.
    Fix: A container's readinessProbe was removed between base and head. Without it, the Service routes traffic to pods that are not yet ready, causing errors during every rollout. Restore the readiness probe.
  • mrs-diff-liveness-probe-removed · Deployment/rtz-gate-demo/gate-web — Deployment rtz-gate-demo/gate-web container 'web' had its livenessProbe removed. Hung or deadlocked containers will no longer be auto-restarted.
    Fix: A container's livenessProbe was removed. Hung or deadlocked containers will no longer be auto-restarted by the kubelet. Restore the liveness probe.
  • mrs-diff-memory-limit-reduced · Deployment/rtz-gate-demo/gate-web — Deployment rtz-gate-demo/gate-web container 'web' memory limit reduced: 128Mi → 32Mi. Risk of OOMKill if usage exceeds the new limit.
    Fix: A container's resources.limits.memory was reduced. If working-set memory exceeds the new limit the container is OOMKilled and restarted. Confirm the new limit reflects observed usage plus headroom.

Cluster-aware checks: on — 51 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