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

Add the PO/rukpak components to the OCP payload

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Critical
    • None
    • None
    • None
    • [OLM-223] Platform Operators, [OLM-224] PO - Pikachu, [OLM-225] PO - Qubernetes
    • 0

    Description

      Goal: Ensure the rukpak/PO components are deployed as CVO-based components during 4.12 that will be gated by tech previews being enabled by an admins.

      Note: The o/platform-operators repository is the only repository that will contain the requisite CVO manifests for 4.12. The downstream rukpak manifests will live in that repository vs. the o/operator-framework-rukpak repository.

      References:

      AC:

      • Open comet requests for the downstream rukpak and PO repositories
      • Get consensus on whether the OLM BZ component will be used for POs, or whether a subcomponent is needed under the OLM component.
      • Add the BZ component/subcomponent to the OWNERS file in both the rukpak and PO repositories.
      • Create a PSSECDEV ticket for having prodsec review the repository contents.
      • Create an ART ticket for adding the PO images to be managed by ART.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1633 The platform-operators-aggregated CO failed to display the resource name

          • 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.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1636 The platform-operators-aggregated cannot be created after enabling TechPreviewNoUpgrade

          • 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.
          • Closed
          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPRUN-2661 Remove rukpak's cert-manager dependency

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPRUN-2662 Ensure rukpak webhooks are deployed using a HA configuration

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPRUN-2666 Add the release.openshift.io/feature-gate annotation to the CVO manifests

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPRUN-2723 Update PlatformOperator's namespace to be PSA compliant

          • 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.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPRUN-2737 Update unpacker pod to be PSA compliant

          • 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.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPRUN-2665 Onboard the o/operator-framework-rukpak repository to CI

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPRUN-2667 Onboard the o/platform-operators repository to CI

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Spike - Represents a research-related task. OPRUN-2746 Spike: Determine what downstream annotations need to be present in CVO manifests [3D]

          • 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.
          • Closed
          links to

          Web Link *: Bump build and tool dependencies in o/platform-operators

          Web Link Add BZ component to OWNERS in o/operator-framework-rukpak

          Web Link Add BZ component to OWNERS in o/platform-operators

          Web Link ci-operator/config: Enable TP features before cluster creation for o/platform-operators in o/release

          Web Link config,manifests: Add the required self-managed-high-availability cluster profile annotation in o/platform-operators

          Web Link Dockerfile: Use COPY instead of ADD for copying the manifests directory in o/platform-operators

          Web Link image source: avoid shadowing /bin with emptyDir mount in o/operator-framework-rukpak

          Web Link Makefile,manifests: Add hack for injecting the self managed HA cluster cluster

          Web Link Makefile,manifests: Reduce the CVO run-level to default 50 level in o/platform-operators

          Web Link Merge the upstream rukpak v0.9.0 tag in o/operator-framework-rukpak

          Web Link Merge the upstream v0.10.0 rukpak tag in o/operator-framework-rukpak

          Web Link OLM-2668 Overview Gist

          GitHub openshift/platform-operators#58: Introduce platform operators to the OCP payload

          Web Link operator/config: Enable TP features before cluster creation in o/release

          Web Link platform/v1alpha1: Add the self managed HA cluster profile in o/api

          Web Link Update the phase 0 API extensions documentation in o/enhancements

          Web Link Update the POC implementation and vendor the PlatformOperators CRD in o/platform-operators

          Web Link Updating ose-cluster-platform-operators-manager images to be consistent with ART

          Web Link Updating ose-olm-rukpak images to be consistent with ART

          Activity

            People

              tflannag@redhat.com Tim Flannagan
              tflannag@redhat.com Tim Flannagan
              Jian Zhang Jian Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: