Delete Managed Kube resources that are no longer used
- Dominant language
- Go
- Stars
- 283
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
The Solr Operator creates many Kubernetes resources while reconciling.
The operator will often choose to create or not create resources depending on the configuration of Solr resource (e.g. a SolrCloud resource). However if a SolrCloud is setup in a way that a resource is needed, and then the setup is changed so the resource is no longer necessary, the operator does not go and garbage collect that resource.
It would be nice to add this additional level of garbage collection to the operator.
We could possibly design this in a way to auto-collect at the end of a reconcile, or just do it on a case-by-case basis for each resource dependency.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the operator's reconcile flow and inventory the Kubernetes resources it conditionally creates for a SolrCloud. Determine how to identify resources that are no longer needed and whether cleanup belongs at the end of reconciliation or with each resource dependency. Done means obsolete resources are garbage-collected while still-needed resources remain managed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100