• nested locking logic (add new lock for route controllers today)
• backport nested locking logic to 4.11
• create route-controller-manager with a minimal subset of exactly what needs to move. keep history as I did before.
• update operator (ideally ingress, but for expediency probably openshift-controller-manager) to install route-controller-manager
• hard to move to ingress operator since it is not build on openshift/library-go but on Operator SDK
• delete route controllers from openshift-controller-manager:  in 4.12 a new repo will be created (route-controller-manager) for the ingress and ingress-ip controllers. This will be managed by OCMO

API side:

• admission of Route is going to be moved as an admission plugin to kube-apiserver as a carry in o/k
• API will still be served by openshift-apiserver
• Route CRD will be created in microshift project and then eventually moved to openshift/api where it will be generated from the type. It will be then consumed by microshift

Leases timeline:

in 4.11.0 we have

1. route-controllers run here behind lease/openshift-controller-manager

in 4.11.z I think we need

1. route-controllers run here behind lease/openshift-controller-manager AND lease/route-controller-manager. This needed so that when upgrading to 4.11.z, we do not end up with a 4.11.0 route-controllers running AND a 4.11.z route-controllers running. The PR as it currently stands would allow the two to run alongside each other

in 4.12, I think we need

1. openshift-controller-manager runs behind lease/openshift-controller-manager
2. route-controller-manager runs behind lease/route-controller-manager