OCPBUGS-29569: Apply hypershift cluster-profile for ibm-cloud-managed

[ashwindasr]

Since HyperShift / Hosted Control Plane have adopted include.release.openshift.io/ibm-cloud-managed, to tailor the resources of clusters running in the ROKS IBM environment, the include.release.openshift.io/hypershift addition will allow Hypershift to express different profile choices than ROKS

[openshift-ci-robot]

@ashwindasr: This pull request references Jira Issue OCPBUGS-29569, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jitendar-singh

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

In response to this:

Since HyperShift / Hosted Control Plane have adopted include.release.openshift.io/ibm-cloud-managed, to tailor the resources of clusters running in the ROKS IBM environment, the include.release.openshift.io/hypershift addition will allow Hypershift to express different profile choices than ROKS

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-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ashwindasr
Once this PR has been reviewed and has the lgtm label, please assign fbm3307 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[fbm3307]

/test okd-images

[openshift-ci]

@ashwindasr: The following tests 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/verify	05764be	link	true	/test verify
ci/prow/okd-e2e-aws-ovn	05764be	link	false	/test okd-e2e-aws-ovn
ci/prow/okd-e2e-aws-ovn-upgrade	05764be	link	false	/test okd-e2e-aws-ovn-upgrade
ci/prow/okd-e2e-aws-operator	05764be	link	false	/test okd-e2e-aws-operator
ci/prow/okd-e2e-aws-ovn-builds	05764be	link	false	/test okd-e2e-aws-ovn-builds
ci/prow/okd-e2e-aws-ovn-jenkins	05764be	link	false	/test okd-e2e-aws-ovn-jenkins
ci/prow/okd-verify	05764be	link	true	/test okd-verify
ci/prow/okd-e2e-aws-ovn-image-ecosystem	05764be	link	false	/test okd-e2e-aws-ovn-image-ecosystem
ci/prow/okd-images	05764be	link	true	/test okd-images

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[metlos]

/retest

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale