OCPBUGS-76367: Include additional operators in OVE config

[bfournie]

Now that the additional operators are available in the 4.21 catalog they should be included in the OVE configuration. This is necessary in order for the operator manifests to be applied correctly.

Note that the 4.22 configuration is using the 4.21 catalog since the operators are not yet available in the 4.22 catalog.

[openshift-ci-robot]

@bfournie: This pull request references Jira Issue OCPBUGS-76367, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

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

Requesting review from QA contact:
/cc @mhanss

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

Details

In response to this:

Now that the additional operators are available in the 4.21 catalog they should be included in the OVE configuration. This is necessary in order for the operator manifests to be applied correctly.

Note that the 4.22 configuration is using the 4.21 catalog since the operators are not yet available in the 4.22 catalog.

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 APPROVED

This pull-request has been approved by: bfournie

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

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

[bfournie]

With is change in a 4.22 installation we can now see the operator manifests correctly applied, for example:

$ oc get nmstate
NAME      STATUS      REASON
nmstate   Available   SuccessfullyDeployed
$ oc get operators/cluster-kube-descheduler-operator.openshift-kube-descheduler-op
NAME                                                              AGE
cluster-kube-descheduler-operator.openshift-kube-descheduler-op   67m
$ oc get NodeHealthCheck -A
NAME                                             AGE
node-healthcheck-self-node-remediation-workers   58m
$ oc get DataProtectionApplication -A
NAMESPACE            NAME         RECONCILED   AGE
assisted-installer   dpa-sample                64m
$ oc get NUMAResourcesOperator -A
NAME            AGE
numaresources   65m

[bfournie]

/verified by @bfournie

[openshift-ci-robot]

@bfournie: This PR has been marked as verified by @bfournie.

Details

In response to this:

/verified by @bfournie

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.

[bfournie]

/cc @andfasano

[openshift-ci]

@bfournie: all tests passed!

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