-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
5
-
False
-
None
-
False
-
OCPPLAN-9555 - Platform Operators
-
[OLM-223] Platform Operators, [OLM-224] PO - Pikachu, [OLM-225] PO - Qubernetes
-
0
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:
- https://docs.ci.openshift.org/docs/how-tos/onboarding-a-new-component/#product-builds-and-becoming-part-of-an-openshift-release-image
- https://source.redhat.com/groups/public/atomicopenshift/atomicopenshift_wiki/guidelines_for_requesting_new_content_managed_by_ocp_art
- https://source.redhat.com/groups/public/atomicopenshift/atomicopenshift_wiki/requesting_a_new_image_or_rpm_to_be_managed_by_art
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.
- causes
-
OCPBUGS-1633 The platform-operators-aggregated CO failed to display the resource name
-
- Closed
-
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
OPRUN-2746 Spike: Determine what downstream annotations need to be present in CVO manifests [3D]
-
- Closed
-
- links to