-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Proactive Architecture
-
False
-
None
-
False
followup to https://issues.redhat.com/browse/WRKLDS-487 and https://issues.redhat.com/browse/WRKLDS-592
- refactor route-controller-manager controllers to use ControllerBuilder from library-go
- openshift-controller-manager-operator refactoring/separating status conditions. Create two instances of the NewDeploymentController to create separate status conditions.
- openshift-controller-manager should be refactored to use NewControllerCommandConfig from library-go which uses genericapiserver. We were very lucky not to need it in this bug https://issues.redhat.com/browse/OCPBUGS-21832?focusedId=23302827&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-23302827 . Unifying this across operators/controllers will help us react better when the next problem occurs.
- remove duplicate passing of kubeconfig into route-controller-manager in hypershift
- clones
-
WRKLDS-592 OCM operator and RCM refactoring
- Closed
1.
|
refactor route-controller-manager controllers | To Do | Unassigned | ||
2.
|
OCMO refactoring/separating status conditions | To Do | Unassigned |