Run on-cluster-builds in separate namespace to OLM

[maschmid]

On OCP 4.20, the on-cluster builds of the Operator bundle and index images fail,

see https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/69430/rehearse-69430-periodic-ci-openshift-knative-serverless-operator-main-ocp4.20-lp-interop-operator-e2e-interop-aws-ocp420/1968994633430077440

The problem is that OCP 4.20 introduces NetworkPolicies in openshift namespaces, so the builds can't pull the UBI image.

A clean solution is to move the builds from OLM_NAMESPACE somewhere else, hence introducing a ON_CLUSTER_BUILDS_NAMESPACE env, defaulting to openshift-serverless-builds for this purpose.

Proposed Changes

• 🐛 Run on-cluster-builds of bundle and index images in a separate namespace (openshift-serverless-builds)

[maschmid]

/test ?

[openshift-ci]

@maschmid: The following commands are available to trigger required jobs:

/test 414-images

/test 414-operator-e2e

/test 414-test-upgrade

/test 419-aws-ovn-images

/test 419-azure-images

/test 419-gcp-images

/test 419-hypershift-images

/test 419-images

/test 419-operator-e2e

/test 419-osd-images

/test 419-single-node-images

/test 419-test-upgrade

/test 419-vsphere-images

/test 420-images

/test 420-operator-e2e

/test 420-test-upgrade

/test ocp4.19-lp-rosa-classic-images

/test ocp4.20-lp-interop-images

The following commands are available to trigger optional jobs:

/test 414-kitchensink-e2e

/test 414-kitchensink-upgrade

/test 414-mesh-e2e

/test 414-mesh-upgrade

/test 414-test-soak

/test 414-ui-e2e

/test 414-upstream-e2e

/test 414-upstream-e2e-kafka

/test 419-kitchensink-e2e

/test 419-kitchensink-upgrade

/test 419-mesh-e2e

/test 419-mesh-upgrade

/test 419-test-soak

/test 419-ui-e2e

/test 419-upstream-e2e

/test 419-upstream-e2e-kafka

/test 420-kitchensink-e2e

/test 420-kitchensink-upgrade

/test 420-mesh-e2e

/test 420-mesh-upgrade

/test 420-test-soak

/test 420-ui-e2e

/test 420-upstream-e2e

/test 420-upstream-e2e-kafka

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-knative-serverless-operator-main-419-images

pull-ci-openshift-knative-serverless-operator-main-419-kitchensink-e2e

pull-ci-openshift-knative-serverless-operator-main-419-kitchensink-upgrade

pull-ci-openshift-knative-serverless-operator-main-419-mesh-e2e

pull-ci-openshift-knative-serverless-operator-main-419-mesh-upgrade

pull-ci-openshift-knative-serverless-operator-main-419-operator-e2e

pull-ci-openshift-knative-serverless-operator-main-419-test-upgrade

pull-ci-openshift-knative-serverless-operator-main-419-upstream-e2e

pull-ci-openshift-knative-serverless-operator-main-419-upstream-e2e-kafka

In response to this:

/test ?

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.

[maschmid]

/test 420-operator-e2e

[maschmid]

/test 420-operator-e2e
/test 419-test-upgrade
/test 419-kitchensink-upgrade

[openshift-ci]

@maschmid: The following test 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/420-operator-e2e	c723720	link	true	/test 420-operator-e2e

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.

[maschmid]

420-operator-e2e will still fail because the Tempo operator is not yet available in OCP 4.20 catalog.

[maschmid]

/test 420-kitchensink-e2e

[cardil]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cardil, maschmid

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

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