mayadata-io / mayadata-io/oep-e2e
Ensure capacity constraint for local PV
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
UseCase: As a developer / admin I need to ensure applications consuming local PVs adhere to capacity specified in PVC specs. However, typical local PVs do not have the intelligence to understand the capacity boundaries & might overshoot the provisioned capacity. This in turn can lead to one application eating up most of the space that is meant for multiple applications using this shared local storage.
This issue shall provide relevant discussions to come up with a solution for above usecase.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the local PV and PVC capacity use case described in the issue, focusing on how applications can exceed the capacity specified in PVC specs. The issue is currently seeking discussion of a solution, so done is an agreed approach for enforcing those capacity boundaries rather than a defined code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100