Epic Goal

• Remove the rukpak CVO manifests from the platform-operators project (rukpak will be managed by new cluster-olm-operator component)
• Update the platform-operators rukpak dependency to be compatible with Rukpak version deployed by new cluster-olm-operator component.

Why is this important?

In 4.14, we are introducing the first tech preview of OLMv1, which consists of three subcomponents (operator-controller, rukpak, and catalogd). With platform-operators and OLMv1 both depending on rukpak, we need to ensure only one instance of rukpak exists on the cluster.

The long-term plan for platform-operators is to have it use the new Operator API directly (i.e. it will no longer depend directly on rukpak).

Therefore, it no longer makes sense to have platform-operators manage the rukpak component.

Scenarios

1. Install an OCP cluster with the TechPreviewNoUpgrade feature gate enabled, and create a PlatformOperator object. All existing platform-operators features should continue to function as expected.

Acceptance Criteria

• When CVO installs platform-operators, rukpak is NOT installed as part of the platform-operators second-level operator
• When CVO completes the installation of a TechPreview cluster, platform-operators starts successfully.
• When a PlatformOperator object is created using a supported package name, the platform-operators controller successfully creates a rukpak BundleDeployment that results in the PlatformOperator being successfully installed.

Dependencies (internal and external)

1. Create minimal OLM v1 second level operator - https://issues.redhat.com/browse/OPECO-2856

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• 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>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>