revert capi-vsphere integration jobs to GKE cluster

[rjsadow]

This PR sends the integration jobs to running on the community GKE cluster due to github rate limit issues.

/cc @chrischdi @sbueringer @killianmuldoon

[killianmuldoon]

/lgtm

[upodroid]

Can we run these jobs on the k8s-infra-prow-build cluster? It should behave the same way as the default(google owned GKE cluster) cluster.

[rjsadow]

Will they? @chrischdi can you help me understand the github rate limit issue a bit more? Is there a unique secret or some other way of obtaining a token that CAPI currently has implemented?

[upodroid]

Yes

I explained on Slack why rate limiting is more frequent in EKS Cluster than in the GKE Clusters. It is to do with the limited set of IPs available for egress traffic. On AWS we are using NAT Gateways but on GCP, every GKE node has it is own IP address so there is a larger pool of egress addresses available.

With regards to getting a token:

• Ask for a read-only token in the #github-management channel on Slack from the existing bot accounts
• Get @ameukam to load it in here https://github.com/kubernetes/k8s.io/blob/be85c5317cada1f9c04b52e4a9d5d581bbd3c1cd/infra/gcp/terraform/k8s-infra-prow-build/prow-build/resources/test-pods/externalsecrets.yaml

[rjsadow]

Thank you for that explanation @upodroid, I've updated the PR to move the jobs to the eks community cluster

[sbueringer]

Thank you!

Will follow-up on the token

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rjsadow, sbueringer

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:

• config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/OWNERS [sbueringer]

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

[sbueringer]

/lgtm

[chrischdi]

/lgtm

[k8s-ci-robot]

@rjsadow: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key cluster-api-provider-vsphere-periodics-main.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-periodics-main.yaml
• key cluster-api-provider-vsphere-periodics-release-1.5.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-periodics-release-1.5.yaml
• key cluster-api-provider-vsphere-periodics-release-1.6.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-periodics-release-1.6.yaml
• key cluster-api-provider-vsphere-periodics-release-1.7.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-periodics-release-1.7.yaml
• key cluster-api-provider-vsphere-periodics-release-1.8.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-periodics-release-1.8.yaml
• key cluster-api-provider-vsphere-presubmits-main.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-presubmits-main.yaml
• key cluster-api-provider-vsphere-presubmits-release-1.5.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-presubmits-release-1.5.yaml
• key cluster-api-provider-vsphere-presubmits-release-1.6.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-presubmits-release-1.6.yaml
• key cluster-api-provider-vsphere-presubmits-release-1.7.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-presubmits-release-1.7.yaml
• key cluster-api-provider-vsphere-presubmits-release-1.8.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-vsphere/cluster-api-provider-vsphere-presubmits-release-1.8.yaml

In response to this:

This PR sends the integration jobs to running on the community GKE cluster due to github rate limit issues.

/cc @chrischdi @sbueringer @killianmuldoon

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.