[ocp4_workload_tenant_namespace] Document pods quota key support#39
Merged
Conversation
The default_quota dict is passed directly as ResourceQuota/CRQ hard limits so `pods` already works without any code change. Add comments making this explicit and showing the recommended usage for multi-tenant clusters where pod count limits are needed. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
wkulhanek
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
podsis a valid key inocp4_workload_tenant_namespace_default_quotafor capping total pod count across all tenant namespaceshardlimits to bothClusterResourceQuotaandResourceQuotapods: "50"example comment to the per-suffix quota block and a note to the default quota variableMotivation
Multi-tenant lab clusters need a pod count ceiling to prevent runaway pod creation (e.g. a student scaling to thousands of small pods). The existing CPU/memory limits don't prevent this since very small pods can be created in large numbers within the resource budget.
Usage