[release-4.15] OCPBUGS-29515: openshift: generate separate manifest for core CAPI CRDs

[damdo]

Manual backport of #195

Store Core CAPI CRDs in their own manifest to get them applied by CVO directly. We want these to be installed independently from whether the cluster-capi-operator is enabled, as other Openshift components rely on them.

This requirement is coming from the need for the SPLAT team to have IPAM core CAPI CRDs in payload even if the platform is not supported.

TODO:

• change replace directive once [release-4.15] OCPBUGS-29515: manifests-gen: store core capi crds also in their own manifest cluster-capi-operator#160 merges

[openshift-ci-robot]

@damdo: This pull request references Jira Issue OCPBUGS-29515, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-29476 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-29476 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
• bug has dependents

Requesting review from QA contact:
/cc @miyadav

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Manual backport of #195

Store Core CAPI CRDs in their own manifest to get them applied by CVO directly. We want these to be installed independently from whether the cluster-capi-operator is enabled, as other Openshift components rely on them.

This requirement is coming from the need for the SPLAT team to have IPAM core CAPI CRDs in payload even if the platform is not supported.

TODO:

• change replace directive once [release-4.15] OCPBUGS-29515: manifests-gen: store core capi crds also in their own manifest cluster-capi-operator#160 merges

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[damdo]

/retest

[damdo]

/retest

[openshift-ci]

@damdo: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-capi-techpreview	b786309	link	false	/test e2e-aws-capi-techpreview

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[JoelSpeed]

/approve
/lgtm
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo, JoelSpeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [JoelSpeed,damdo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sunzhaohua2]

/label cherry-pick-approved

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD db1841a and 2 for PR HEAD b786309 in total

[openshift-ci-robot]

@damdo: Jira Issue OCPBUGS-29515: All pull requests linked via external trackers have merged:

• openshift/cluster-capi-operator#160
• openshift/cluster-api#198

Jira Issue OCPBUGS-29515 has been moved to the MODIFIED state.

Details

In response to this:

Manual backport of #195

Store Core CAPI CRDs in their own manifest to get them applied by CVO directly. We want these to be installed independently from whether the cluster-capi-operator is enabled, as other Openshift components rely on them.

This requirement is coming from the need for the SPLAT team to have IPAM core CAPI CRDs in payload even if the platform is not supported.

TODO:

• change replace directive once [release-4.15] OCPBUGS-29515: manifests-gen: store core capi crds also in their own manifest cluster-capi-operator#160 merges

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-api-container-v4.15.0-202402290407.p0.gc3b9ac8.assembly.stream.el9 for distgit ose-cluster-api.
All builds following this will include this PR.