platform/v1alpha1: Update the cluster profile annotations

[timflannagan]

Update the PlatformOperator CRD and add the required self-managed-high-availability cluster profile.

Signed-off-by: timflannagan timflannagan@gmail.com

[openshift-ci]

Hello @timflannagan! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

For merging purposes, this repository follows the no-Feature-Freeze process which means that in addition to the standard lgtm and approved labels this repository requires either:

bugzilla/valid-bug - applied if your PR references a valid bugzilla bug

OR

qe-approved, docs-approved, and px-approved - these labels can be applied by anyone in the openshift org via the /label <labelname> command.

Who should apply these qe/docs/px labels?

• For a no-Feature-Freeze team who is merging a feature before code freeze, they need to get those labels applied to their api repo PR by the appropriate teams (i.e. qe, docs, px)
• For a Feature Freeze (traditional) team who is merging a feature before FF, they can self-apply the labels (via /label commands), they are basically irrelevant for those teams
• For a Feature Freeze team who is merging a feature after FF, the PR should be rejected barring an exception

[jianzhangbjz]

/assign @bparees

[timflannagan]

I wasn't able to easily run any of the Makefile update/verify related targets locally so I had to manually inspect the prowjob failures to determine what changes are needed. The last force push should (hopefully ™️) fix that failing verification check.

[timflannagan]

@bparees Do you have time to take another look at this? We're just removing the hacks that are in-tree for the o/platform-operators repository: https://github.com/openshift/platform-operators/blob/main/Makefile#L80-L83, and it would be nice to get this in before end of sprint 225 to avoid needing to create a bug.

[bparees]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, timflannagan

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 [bparees]

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

[timflannagan]

We're doing the TE slides so manually adding the px-approved label. See https://coreos.slack.com/archives/C030W4V9BHN/p1661875975344669 for more information.

/label px-approved

[adellape]

/label docs-approved

[timflannagan]

Holding for QE approval. This is a no-op while we work towards removing the hacks in the o/platform-operators repository that already contain these cluster profile annotations.

/assign jianzhangbjz
/hold

[jianzhangbjz]

/label qe-approved
/unhold

[openshift-ci]

@timflannagan: all tests passed!

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