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

Move node-ca to another operator

    XMLWordPrintable

Details

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

    Description

      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>

       

      Attachments

        Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. IR-351 Make Image Registry Operator Optional

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Release Pending
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MCO-499 The MCD should manage certificates via a separate, non-MC path

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Release Pending

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: