actions / actions/actions-runner-controller
Ability to remove persistent volumes.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
Ability to remove persistent volumes.
A feature to set to delete unbounded PVs after ie. x-amount of minutes.
Why is this needed?
Currently, there seems to be no way to delete PVs at all (even if having reclaim policy delete) meaning on systems like GKE we will end up with PVs running without use overnight or over the weekends.
Cheers
Contributor guide
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
No files, tests, or entry points are named. Start by tracing how the controller observes and reconciles persistent volumes, then define the reclaim behavior and configuration needed for unbound PV cleanup; done means the feature safely removes eligible volumes after the configured interval and is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100