Reduce # of PVCs used in Dev
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**Describe the task**
We spin up PVCs for nats, statefulsets, tileserv backups, wal logs, etc.
Platform Services has a limit set to 60 PVCs per namespace, which we hit easily when we have multiple dev deployments.
We can limit the # of PVCs in dev by sharing PVCs and namespacing them based on subpaths
See linked SO thread in additional context.
**Acceptance Criteria**
- [ ] PVCs per dev deployment are minimized
**Additional context**
Solution options:
- Ephemeral storage: https://stackoverflow.developer.gov.bc.ca/a/996/16
- Sharing PVC sub paths: https://stackoverflow.developer.gov.bc.ca/questions/973
Contributor guide
Research direction
The issue names no files, tests, or entry points. Review the linked Stack Overflow discussions and inventory PVCs for NATS, StatefulSets, tile-server backups, and WAL logs across dev deployments; done means dev deployments use fewer PVCs and remain functional under the namespace limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100