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

[upstream] Integrate Operator controller with Rukpak

XMLWordPrintable

    • Integrate Operator controller with Rukpak
    • 8
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-443 - [Phase 1 MVP/Tech Preview] OLM 1.0 - Extension Installation (F7)
    • OCPSTRAT-443[Phase 1 MVP/Tech Preview] OLM 1.0 - Extension Installation (F7)
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • The Operator Controller will take a solution set from Deppy and ensure that a single bundleDeployment exists for each entity. 

      Why is this important?

      •  Once Deppy has identified that the list of constraints introduced by the Operator CRs on cluster, the Operator Controller will need to identify what manifests needs to be applied to the cluster, which can only be accomplished by converting a deppy entity ID to an operator in a catalogSource. Once the manifests are acquired, the operator controller then needs to ensure that the bundleDeployments are created on cluster for each entity.

      Scenarios

      1. Given a solution set, the Operator Controller can resolve entity IDs to the associated packageName and bundle image.
      2. For each entity in the solution set, the Operator Controller ensures that a single bundleDeployment exists.
      3. If there is an issue retrieving the content for an entity ID, an error message is surfaced in the Operator CR. 

      Acceptance Criteria

      •  CI - MUST be running successfully with tests automated
      • The Operator Controller can resolve entities in a solution set to an operator within an available catalogSource.
      • The Operator Controller can retrieve the manifests associated with the operator the user wishes to install.
      • The Operator Controller can surface errors when attempting to retrieve the manifests associated with an entity included in the solution set. 

      Dependencies (internal and external)

      1. https://issues.redhat.com/browse/OLM-2832 and https://issues.redhat.com/browse/OLM-2770 must be completed if this work is to be driven through the Operator API introduced in https://issues.redhat.com/browse/OLM-2830
      2. Until the epics mentioned in bullet point 1 are completed, a hard coded solution set can be used to implement and test this feature. This requires the solution set interface to be defined. 

      Previous Work (Optional):

      1. N/A

      Upstream Issues:

      Open questions:

      1. N/A

      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>

       

       

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

              Created:
              Updated: