Uploaded image for project: 'Operator Runtime'
  1. Operator Runtime
  2. OPRUN-2862

[upstream] Kubectl Operator Plugin Supports OLM V1 Install and Uninstall Workflows

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • openshift-4.14
    • Cleanup Uninstalled Operators
    • 5
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-411 - [Phase 1 MVP/Tech Preview] OLM 1.0 - Extension Removal (F16)
    • OCPSTRAT-411[Phase 1 MVP/Tech Preview] OLM 1.0 - Extension Removal (F16)
    • 0% To Do, 0% In Progress, 100% Done
    • 0

      Epic Goal

      • The goal of this epic is to ensure that operators can be installed and uninstalled with commands from the kubectl operator plugin that rely on the cluster having the operator controller installed.

      Why is this important?

      • Providing a kubectl plugin that simplifies the install and uninstall process provides the user with a first class experience when managing operators.

      Scenarios

      1. I want to install an operator using the kubectl operator plugin.
      2. I have installed an operator using the Operator API and now wish to uninstall it using the kubectl operator plugin.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated.
      • Kubectl operator plugin can install an operators by creating an Operator CR.
      • Kubectl operator plugin can uninstall an operator by deleting an Operator CR.

      Dependencies (internal and external)

      1. N/A

      Previous Work (Optional):

      1. N/A

      Upstream Issues:

      • Needs to be created.

      Open questions:

      1. Should CRDs be removed by default, which can potentially result in dataloss for services deployed on the cluster.
        • We have decided that deleting an Operator CR deletes the associated CRD.

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • 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>

       

            agreene1991 Alexander Greene
            agreene1991 Alexander Greene
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: