Uploaded image for project: 'OpenShift Console'
  1. OpenShift Console
  2. CONSOLE-3160

Make console operator optional



    • Make console operator optional
    • True
    • Waiting for a fix from the auth team: https://issues.redhat.com/browse/AUTH-319
    • False
    • To Do
    • OCPPLAN-7589 - OpenShift Optional Capabilities (Phases 1 & 2)
    • Impediment
    • 100
    • 100% 100%


      Epic Goal

      • Make it possible to disable the console operator at install time, while still having a supported+upgradeable cluster.

      Why is this important?

      • It's possible to disable console itself using spec.managementState in the console operator config. There is no way to remove the console operator, though. For clusters where an admin wants to completely remove console, we should give the option to disable the console operator as well.


      1. I'm an administrator who wants to minimize my OpenShift cluster footprint and who does not want the console installed on my cluster

      Acceptance Criteria

      • It is possible at install time to opt-out of having the console operator installed. Once the cluster comes up, the console operator is not running.

      Dependencies (internal and external)

      1. Composable cluster installation

      Previous Work (Optional):

      1. https://docs.google.com/document/d/1srswUYYHIbKT5PAC5ZuVos9T2rBnf7k0F1WV2zKUTrA/edit#heading=h.mduog8qznwz
      2. https://docs.google.com/presentation/d/1U2zYAyrNGBooGBuyQME8Xn905RvOPbVv3XFw3stddZw/edit#slide=id.g10555cc0639_0_7

      Open questions::

      1. The console operator manages the downloads deployment as well. Do we disable the downloads deployment? Long term we want to move to CLI manager: https://github.com/openshift/enhancements/blob/6ae78842d4a87593c63274e02ac7a33cc7f296c3/enhancements/oc/cli-manager.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>


        Issue Links



              pakratoc@redhat.com Pavel Kratochvil
              spadgett@redhat.com Samuel Padgett
              Zhang Yanping Zhang Yanping
              0 Vote for this issue
              13 Start watching this issue