Uploaded image for project: 'OpenShift Cloud Credential Operator'
  1. OpenShift Cloud Credential Operator
  2. CCO-493

Make Cloud Credential Operator optional for remaining providers and topologies


    • Make Cloud Credential Operator optional
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-1308 - OpenShift Optional Capabilities (Phase 7)
    • OCPSTRAT-1308OpenShift Optional Capabilities (Phase 7)
    • 100% To Do, 0% In Progress, 0% Done
    • S

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Make it possible to entirely disable the Cloud Credential Operator optional by leveraging the Composable OpenShift capability.
      • Complete the work not completed in CCO-419 / OCPEDGE-69, which only covered baremetal and SNO

      Why is this important?

      • Make it possible for customers and Red Hat teams producing OCP distributions/topologies/experiences to enable/disable some CVO components while still keeping their cluster supported.


      1. This feature must consider the different deployment footprints including self-managed and managed OpenShift, connected vs. disconnected (restricted and air-gapped), supported topologies (standard HA, compact cluster, SNO), etc.
      2. Enabled/disabled configuration must persist throughout cluster lifecycle including upgrades.
      3. If there's any risk/impact of data loss or service unavailability (for Day 2 operations), the System must provide guidance on what the risks are and let user decide if risk worth undertaking.


      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      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>

            Unassigned Unassigned
            julim Ju Lim
            Jianping Shu Jianping Shu
            Eric Rich Eric Rich
            0 Vote for this issue
            5 Start watching this issue