Add resource management and multi-team scaling guide#950
Add resource management and multi-team scaling guide#950
Conversation
k1sauce
requested review from
EngHabu,
cosmicBboy,
kumare3,
ppiegaze and
samhita-alla
as code owners
Deploying docs with
|
| Latest commit: |
2b632ee
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c58dfed3.docs-dog.pages.dev |
| Branch Preview URL: | https://add-resource-management-guid.docs-dog.pages.dev |
There was a problem hiding this comment.
Pull request overview
Adds a new “Project patterns” guide page focused on structuring projects/domains and managing resources (quotas + task resources) as organizations scale to multiple teams, and links it from the project-patterns index. The page also includes a roadmap section describing the upcoming v2 quota model.
Changes:
- Added
resource-management.mdguide covering project/domain isolation, quotas, task-level resources, RBAC/secrets, and multi-team scaling patterns. - Documented a v2 quota roadmap section (current state, architecture changes, migration notes).
- Linked the new guide from
content/user-guide/project-patterns/_index.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| content/user-guide/project-patterns/resource-management.md | New documentation page describing multi-team resource management patterns and v2 quota roadmap. |
| content/user-guide/project-patterns/_index.md | Adds a link-card entry for the new resource management guide. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ### Be explicit about ephemeral storage | ||
|
|
||
| The `disk` default is zero, which means a task pod will consume node storage as needed. A pod can be evicted if the node runs short on storage. Any team doing heavy data processing should always set `disk` explicitly: |
There was a problem hiding this comment.
“The disk default is zero” doesn’t match the Resources API/docs where disk is optional (i.e., unset by default). Suggest describing it as “unset/no ephemeral-storage request/limit is applied by default”, and then explain the eviction risk when node storage is pressured.
| The `disk` default is zero, which means a task pod will consume node storage as needed. A pod can be evicted if the node runs short on storage. Any team doing heavy data processing should always set `disk` explicitly: | |
| By default, `disk` is unset, so no ephemeral-storage request or limit is applied. A task pod can still consume node storage as needed, and it may be evicted if the node comes under storage pressure. Any team doing heavy data processing should always set `disk` explicitly: |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
@k1sauce Can you address the copilot comments. They seem legit to me (but I might be wrong) |
|
@ppiegaze do we need to run |
Adds a new project-patterns page covering projects/domains, quotas, RBAC, secrets, and multi-team scaling patterns. Also documents the v2 quota roadmap.