NatLabRockies / NatLabRockies/openstudio-server-helm

Docs: ResourceQuota sizing guidance for fleets > 2800 pods

Open
#116 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go Template
Stars
12
Forks
24
PR merge metrics
No merged PRs in 30d

Description

Summary

During the 2026-08-24 scale-up campaign, the existing ResourceQuota became a wedge above ~2800 pods (see CAMPAIGN-RECORD-20260824 / PR #113). Quota manifests were sized for the old fleet ceiling.

Task

Document quota sizing guidance before anyone re-applies a resource-quota manifest:

  • Observed pod-count ceilings per quota configuration
  • Recommended pods quota (and any compute quotas) for target fleet sizes: ~300, ~2800, ~9000
  • Where the guidance lives (runbook or values.yaml comment near any quota template)

Context

The quota was not re-applied during the campaign precisely because its sizing was unknown; this issue prevents a repeat of that discovery-by-outage.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with CAMPAIGN-RECORD-20260824 and PR #113, then inspect the resource-quota manifest and any values.yaml quota template. Record observed pod ceilings and determine recommended pods and compute quotas for fleets of about 300, 2800, and 9000 pods. Put the guidance in a runbook or a values.yaml comment near the quota template.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
documentation, infrastructure
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.