uselagoon / uselagoon/remote-controller
Clean up expiring namespaces
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 2
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
During migrations of environments from one target to another, the old namespace remains in the old target after migrations are performed, and could be forgotten about.
It could be useful to scan namespaces for a label like lagoon.sh/expiration=${timestamp} and then perform a deletion of that namespace.
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 locating the controller entry points that manage namespaces and reviewing how namespace labels and migration targets are handled. Confirm how the expiration timestamp should be interpreted, then verify that namespaces carrying an expired label are deleted without affecting active environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100