ci-operator/config/openshift/router: Generic e2e-aws -> e2e for 4.6+

[wking]

Following the pattern from e7bb102 (#10152), the e2e-aws -> e2e change declares the router presubmits to be platform-agnostic.

The AWS -> GCP change takes advantage of the platform-agnosticism to shift CI load from AWS (where we're currently pegging Boskos lease capacity) to GCP (where we have some spare lease capacity).

Procedure docs in flight in #10166.

[openshift-ci-robot]

@wking: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/router/release-4.7/e2e	34bdc50	link	/test pj-rehearse
ci/rehearse/openshift/router/master/e2e-upgrade	34bdc50	link	/test pj-rehearse
ci/rehearse/openshift/router/release-4.7/e2e-upgrade	34bdc50	link	/test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[Miciah]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miciah, wking

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/router/OWNERS [Miciah]
• ci-operator/jobs/openshift/router/OWNERS [Miciah]

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

[openshift-ci-robot]

@wking: Updated the following 9 configmaps:

• ci-operator-4.7-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-router-release-4.7.yaml using file ci-operator/config/openshift/router/openshift-router-release-4.7.yaml
• job-config-master configmap in namespace ci at cluster api.ci using the following files:
  • key openshift-router-master-presubmits.yaml using file ci-operator/jobs/openshift/router/openshift-router-master-presubmits.yaml
• job-config-4.6 configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-router-release-4.6-presubmits.yaml using file ci-operator/jobs/openshift/router/openshift-router-release-4.6-presubmits.yaml
• job-config-4.6 configmap in namespace ci at cluster api.ci using the following files:
  • key openshift-router-release-4.6-presubmits.yaml using file ci-operator/jobs/openshift/router/openshift-router-release-4.6-presubmits.yaml
• job-config-4.7 configmap in namespace ci at cluster api.ci using the following files:
  • key openshift-router-release-4.7-presubmits.yaml using file ci-operator/jobs/openshift/router/openshift-router-release-4.7-presubmits.yaml
• job-config-4.7 configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-router-release-4.7-presubmits.yaml using file ci-operator/jobs/openshift/router/openshift-router-release-4.7-presubmits.yaml
• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-router-master.yaml using file ci-operator/config/openshift/router/openshift-router-master.yaml
• ci-operator-4.6-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-router-release-4.6.yaml using file ci-operator/config/openshift/router/openshift-router-release-4.6.yaml
• job-config-master configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-router-master-presubmits.yaml using file ci-operator/jobs/openshift/router/openshift-router-master-presubmits.yaml

Details

In response to this:

Following the pattern from e7bb102 (#10152), the e2e-aws -> e2e change declares the router presubmits to be platform-agnostic.

The AWS -> GCP change takes advantage of the platform-agnosticism to shift CI load from AWS (where we're currently pegging Boskos lease capacity) to GCP (where we have some spare lease capacity).

Procedure docs in flight in #10166.

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.