operators [CI] ibmcloud-operator (1.0.12)

[JohnStarich]

Automated release of IBM Cloud Operator v1.0.12.

[openshift-ci]

Hi @JohnStarich. Thanks for your PR.

I'm waiting for a redhat-openshift-ecosystem 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/test-infra repository.

[github-actions]

Automatic Cluster Version Label (OCP) - packagemanifest only

Starting OCP v4.9 (based on k8s 1.22) some old API were deprecated(Deprecated API Migration Guide from v1.22, OKD/OpenShift Catalogs criteria and options). User can set com.redhat.openshift.versions: <versions>in its bundle annotations.yaml file to limit specific operator version to be visible on certain cluster.
Users can set label only when the operator is in bundle format. For packagemanifest format it is not possible to set this lablel, but community-operators pipeline can automatically set such label to the bundle. User have to allow it by putting packagemanifestClusterVersionLabel: auto in ci.yaml file

$ cat <path-to-operator>/ci.yaml
packagemanifestClusterVersionLabel: auto

More info here.

[mvalarh]

@JohnStarich please add following line in to ci.yaml

packagemanifestClusterVersionLabel: auto

[mvalarh]

/test 4.9-deploy-operator-on-openshift

[framework-automation]

/merge possible

[framework-automation]

/merge possible