Uploaded image for project: 'OpenShift Image Registry'
  1. OpenShift Image Registry
  2. IR-230

Move node-ca to another operator

XMLWordPrintable

    • Move node-ca to another operator
    • False
    • False
    • To Do
    • OCPSTRAT-36 - OpenShift Optional Capabilities (Phase 4)
    • OCPSTRAT-36OpenShift Optional Capabilities (Phase 4)
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • node-ca should be present on the cluster even if the cluster image registry operator is not installed.

      Why is this important?

      • We want to make the operator optional.

      Scenarios

      1. As an OpenShift engineer, I want node-ca to be managed by something else that exists without the cluster image registry operator.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated

      Enhancement Proposal

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>

       

              fmissi Flavian Missi
              obulatov@redhat.com Oleg Bulatov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: