Switch e2e and e2e-upgrade jobs to gcp in-keeping with current norms

[marun]

No description provided.

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/oauth-server/master/e2e-gcp-serial	c931ab78c5fdbb765d13e22da539cd5220d28ce0	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.

[sttts]

/lgtm
/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marun, sttts

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/oauth-server/OWNERS [sttts]
• ci-operator/jobs/openshift/oauth-server/OWNERS [sttts]

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]

@marun: Updated the following 3 configmaps:

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

Details

In response to this:

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.

[wking]

If you are platform-agnostic, can we name these e2e? Then you can pivot the backing platform as needed without having Prow get confused about the jobs being renamed. Docs. Examples: #10152, #10179, #10180, #10377.

[marun]

The platform being targeted seems like a useful detail to expose. prow confusion is temporary, and how often do we really pivot jobs to different platforms?

[wking]

The platform being targeted seems like a useful detail to expose.

It's still available if you need it. I don't see why it needs top billing in the job names on preflights for platform-agnostic repositories.

prow confusion is temporary, and how often do we really pivot jobs to different platforms?

This would be the fourth or fifth repo to pivot in the past month. By declaring yourself platform agnostic with a generic job name, you create a larger pool of reschedulable jobs that can be shifted to mitigate future capacity issues.