openshift / openshift/oadp-operator
Make `replicaset.spec.revisionHistoryLimit` configurable
Open
Nobody has claimed this yet.
lifecycle/frozen
- Dominant language
- Go
- Stars
- 92
- Forks
- 93
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 43
Description
As documented, ReplicaSets can become left out in cluster
https://github.com/openshift/oadp-operator/blob/master/docs/install_olm.md#verify-install
This can reproduced when testing upgrades
NAME DESIRED CURRENT READY AGE
replicaset.apps/openshift-adp-controller-manager-686685cc8f 1 1 1 4m33s
replicaset.apps/openshift-adp-controller-manager-77c584bf8b 0 0 0 6m33s
replicaset.apps/velero-5fdf7d65df 1 1 1 118s
replicaset.apps/velero-6bf5469f9c 0 0 0 5m40s
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
Start with docs/install_olm.md#verify-install and the ReplicaSet output in the issue. Trace how upgrades create these ReplicaSets and where the operator can expose spec.revisionHistoryLimit as a configurable value. Done means the setting can be configured and upgrade verification no longer leaves unnecessary ReplicaSets behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100