serverless-operator - cluster pools for OCP 4.8

[mgencur]

• Configures OCP 4.8 for pre-submit checks on main branch instead of OCP 4.7
• Configures OCP 4.8 for weekly jobs on Azure, GCP, vSphere, AWS OVN
• Configures claim-based clusters (cluster-pools) only for OCP 4.8 on AWS, but excluding ServiceMesh tests which currently fail there

[mgencur]

/retest

[mgencur]

The Azure failure was consistent, apparently there was a regression in CI. It has been fixed by #20978 . The related Slack discussion: https://coreos.slack.com/archives/C01CQA76KMX/p1628263200233100
Re-running the Azure job to see the successful run.

[mgencur]

/retest

[openshift-ci]

@mgencur: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Rerun command
ci/rehearse/periodic-ci-openshift-knative-serverless-operator-main-4.8-vsphere-e2e-vsphere-ocp-48-continuous	182cbc9	link	/test pj-rehearse
ci/rehearse/periodic-ci-openshift-knative-serverless-operator-main-4.8-upgrade-tests-aws-ocp-48-continuous	182cbc9	link	/test pj-rehearse
ci/rehearse/openshift-knative/serverless-operator/main/4.8-upstream-e2e-mesh-aws-ocp-48	182cbc9	link	/test pj-rehearse
ci/rehearse/periodic-ci-openshift-knative-serverless-operator-main-4.6-upgrade-tests-aws-ocp-46-continuous	182cbc9	link	/test pj-rehearse
ci/prow/pj-rehearse	182cbc9	link	/test pj-rehearse

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

[markusthoemmes]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: markusthoemmes, mgencur

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:

• ci-operator/config/openshift-knative/serverless-operator/OWNERS [markusthoemmes,mgencur]
• ci-operator/jobs/openshift-knative/serverless-operator/OWNERS [markusthoemmes,mgencur]

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

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[openshift-ci]

@mgencur: Updated the following 2 configmaps:

• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-knative-serverless-operator-main__4.6.yaml using file ci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.6.yaml
  • key openshift-knative-serverless-operator-main__4.7.yaml using file ci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.7.yaml
  • key openshift-knative-serverless-operator-main__4.7-aws-ovn.yaml using file ``
  • key openshift-knative-serverless-operator-main__4.8-aws-ovn.yaml using file ci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.8-aws-ovn.yaml
  • key openshift-knative-serverless-operator-main__4.7-azure.yaml using file ``
  • key openshift-knative-serverless-operator-main__4.8-azure.yaml using file ci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.8-azure.yaml
  • key openshift-knative-serverless-operator-main__4.7-gcp.yaml using file ``
  • key openshift-knative-serverless-operator-main__4.8-gcp.yaml using file ci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.8-gcp.yaml
  • key openshift-knative-serverless-operator-main__4.7-vsphere.yaml using file ``
  • key openshift-knative-serverless-operator-main__4.8-vsphere.yaml using file ci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.8-vsphere.yaml
  • key openshift-knative-serverless-operator-main__4.8.yaml using file ci-operator/config/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main__4.8.yaml
• job-config-master configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-knative-serverless-operator-main-periodics.yaml using file ci-operator/jobs/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main-periodics.yaml
  • key openshift-knative-serverless-operator-main-postsubmits.yaml using file ci-operator/jobs/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main-postsubmits.yaml
  • key openshift-knative-serverless-operator-main-presubmits.yaml using file ci-operator/jobs/openshift-knative/serverless-operator/openshift-knative-serverless-operator-main-presubmits.yaml

Details

In response to this:

• Configures OCP 4.8 for pre-submit checks on main branch instead of OCP 4.7
• Configures OCP 4.8 for weekly jobs on Azure, GCP, vSphere, AWS OVN
• Configures claim-based clusters (cluster-pools) only for OCP 4.8 on AWS, but excluding ServiceMesh tests which currently fail there

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.