Skip to content

fix(resource-quotas): bump vault quota for 256Mi per-pod requests#39

Merged
danielgines merged 1 commit intomainfrom
fix/vault-quota-bump
May 1, 2026
Merged

fix(resource-quotas): bump vault quota for 256Mi per-pod requests#39
danielgines merged 1 commit intomainfrom
fix/vault-quota-bump

Conversation

@danielgines
Copy link
Copy Markdown
Member

Vault sts rolling-update blocked because ResourceQuota was sized for 128Mi/pod (chart default). Block 3 right-sizing bumped to 256Mi/pod, 3-pod total 768Mi > 600Mi quota. Bumps to 1200Mi to fit 4-pod surge with 200Mi tracker headroom.

Audit on cortex prd 2026-04-30 found vault sts blocked from rolling
update because the namespace ResourceQuota platform-quota-vault was
sized for chart-default 128Mi req per pod (3-pod baseline 384Mi <
600Mi quota). After Block 3 right-sizing bumped the per-pod request
to 256Mi (peak observed ~190Mi), the 3-pod total (768Mi) exceeds the
600Mi quota — sts-controller cannot create the 4th surge pod during
rolling-update, blocking config rollout.

Bumps quota to:
  requests.cpu     300m    -> 1
  requests.memory  600Mi   -> 1200Mi
  limits.cpu       1500m   -> 2
  limits.memory    1500Mi  -> 2400Mi

Sized for 4-pod surge at 256Mi req per pod = 1024Mi + 200Mi tracker
headroom = 1200Mi total.
@danielgines danielgines merged commit 55ab58b into main May 1, 2026
5 checks passed
@danielgines danielgines deleted the fix/vault-quota-bump branch May 1, 2026 01:48
danielgines added a commit that referenced this pull request May 1, 2026
Sync chart Chart.yaml + values.yaml to match the resource-quotas/values.yaml
vault-quota bump merged in #39 (3-file rule).
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