Problem:

As an Infrastructure, Administrator, I don't want nor need the Cloud Credential Operator (CCO) deployed when I deploy OpenShift in baremetal environments (where it's not applicable), as I don't want to use or pay for resources needed to operate the CCO operator.

Goal:

Make it possible to disable CCO at install time, while still having a supported and upgradeable cluster.
CCO-215 - Investigate scope for 4.12 to be part of OCPPLAN-7589 (Composable OpenShift).

Why is it important?

Being able to disable the entire operator will provide a simpler and optimized install experience that gives a more desirable result for bare metal OpenShift installations.

Acceptance criteria

At install time, the Admin can opt-out of having the CCO installed. Once the cluster comes up, the CCO is not running and not present in the cluster.

Dependencies (External/Internal)

Depends on the optional capabilities feature (OCPPLAN-7589) to be implemented in the Installer and CVO.

Previous Work (Optional):

• Composable Install
• Composable OpenShift

Design Artifacts

See the capabilities enhancement proposal here:
https://github.com/openshift/enhancements/blob/master/enhancements/installer/component-selection.md

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>