-
Story
-
Resolution: Done
-
Minor
-
None
-
None
-
2
-
False
-
None
-
False
-
-
-
Sprint 249, Sprint 248, Sprint 243, Sprint 244, Sprint 245, Sprint 246, Sprint 247, Sprint 250, OpenShift SPLAT - Sprint 253
*USER STORY:*
As an OpenShift partner, I want instructions for the external platform on when to run CCMs so that I can ensure proper installation.
*DESCRIPTION:*
As described in the "Bootstrap Changes" section of the enhancement Add support for out-of-tree cloud provider integration , there are special considerations that must be followed when starting the CCMs.
In specific, the CCCMO is the first operator to run on the control plane as the CCMs are responsible for initializing node objects. For integrated providers, the CCCMO will start the proper CCM during bootstrap. On the external platform, users will need to inject a manifest for their CCM into the installation artifacts, and it will need to run early enough that it will initialize the control plane names. The CCM also needs to take into account the "Uninitialized" and "NotReady" taints.
This card is about creating guidance for the OpenShift Infrastructure Onboarding Guide to detail what a partner needs to do to enable their CCM during the bootstrap phase.
*Required:*
- Documentation added to the infrastructure onboarding guide to detail how the CCM works during bootstrap and what partners will need to do.
*Nice to have:*
- pointer to an example, perhaps the OCI work
*ACCEPTANCE CRITERIA:*
- Documentation confirmed and merged into site
*ENGINEERING DETAILS:*
This should be relatively straightforward process of detailing what taints the CCM needs to tolerate, and how to inject the CCM manifest so that it runs early. The latter point might require some research.