-
Spike
-
Resolution: Done
-
Normal
-
None
-
None
-
3
-
False
-
None
-
False
-
-
-
CLOUD Sprint 240
As part of the external platform, partners can deploy their own cloud controller managers (CCMs) to openshift. Because this activity involves running a new core component in openshift, we should provide guidance to our partners about the preferred methods for deployment.
There are several different methodologies which could be employed to achieve the result of deploying an external CCM in openshift: from a simple manifest to a full operator. The output of this card should be a document which describes the different methods, their advantages and disadvantages, and relative efforts involved with creating each. Ideally, this document will inform our next decisions about which deployment methodology to invest resources in creating.
From Joel: Please include a "do nothing" option where we provide zero code or integration and just allow the end user to do their own thing, all our operator does is apply a deployment at the end of the day. And a "do nothing B" option with a test suite similar to what we have already in CCMO
DoD:
- Create a document to outline different options for deploying the CCMs
- Include how testing CCMs fits into this
- is related to
-
OCPSTRAT-542 [Phase Next] Add a new platform type ("external") to identify clusters with non-integrated partner components enabled
- New
- links to