OSD-28131: Deploying COO in place of OBO on SC clusters

[Nikokolas3270]

This PR removes OBO subscription from Hypershift service clusters (SCs)

The following MR install COO on those clusters:
https://gitlab.cee.redhat.com/service/osd-fleet-manager/-/merge_requests/1043

This MR must be merged after above PR

[openshift-ci-robot]

@Nikokolas3270: This pull request references OSD-28131 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

Do not merge yet

COO is deployed through the "Red Hat" catalog.
However it is not 100% sure if COO will be deployed through this catalog.
Below article seems to imply that the operator will be deployed through one of the default catalog... and "Red Hat" is one of them:
https://access.redhat.com/articles/7103797

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]

Hi @Nikokolas3270. Thanks for your PR.

I'm waiting for a rhobs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[jan--f]

@Nikokolas3270 @apahim is still pr still required?

[openshift-ci-robot]

@Nikokolas3270: This pull request references OSD-28131 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

This PR removes OBO subscription from Hypershift service clusters (SCs)

The following MR install COO on those clusters:
https://gitlab.cee.redhat.com/service/osd-fleet-manager/-/merge_requests/1043

This MR must be merged after above PR

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.

[Nikokolas3270]

@Nikokolas3270 @apahim is still pr still required?

@jan--f , yes it is still required... but most of the code moved there:
https://gitlab.cee.redhat.com/service/osd-fleet-manager/-/merge_requests/1043

[jan--f]

/lgtm
/approve

[jan--f]

/hold
for https://gitlab.cee.redhat.com/service/osd-fleet-manager/-/merge_requests/1043

[jan--f]

/lgtm

[jan--f]

/retest

[jan--f]

Checkout the commit lint results. We follow conventional commits. A prefix of chore: should fix it.

[jan--f]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f, Nikokolas3270

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jan--f]

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