-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
After the installation is done, CVO should be able to figure out what capabilities are installed and reconcile them.
We can ignore, for now, "what happens if someone adjust spec.capabilities day 2?" and "what happens if someone updates to a new release?". Both of those will be addressed in follow-up work.
Here are work items
- Polling CVO object earlier in the process than it is now.
- Code to handle the capabilities
- blocks
-
OTA-572 CVO complains in status.conditions that it can not drop a capability in spec.capabilities
- Closed
-
OTA-574 CVO taints in previously-reconciled manifests on updates
- Closed
-
OTA-582 Create a library-go Manifest.Include method
- Closed
- is blocked by
-
OTA-596 Poll for cluster version object earlier in startup
- Closed
-
OTA-566 openshift/api vendor bump to pick up new ClusterVersion CRD
- Closed
- links to