Run upstream tests currently using kube-up on top of CAPV

[chrischdi]

Describe the solution you'd like

The plan is to setup the same tests as:

• ci-kubernetes-gce-conformance-latest
• ci-kubernetes-e2e-gci-gce-alpha-features
• ci-kubernetes-e2e-gci-gce-serial
• ci-kubernetes-e2e-gci-gce-slow
• ci-kubernetes-e2e-gci-gce

But run them on top of CAPV.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Mailinglist:
https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/igg420CDQJg/m/z55dW2WDBQAJ

Environment:

• Cluster-api-provider-vsphere version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[sbueringer]

/assign @chrischdi
(just to make it visible that you're currently working on it)

[chrischdi]

Action plan:

• Merge PR which adds configuration file for all cases for kubetest
  • 🌱 Add kubetest files for upstream e2e tests #2417
• Merge fix PR:
  • Check timeout on govmomi calls #2453
• Create test-infra PR to add periodic jobs which make use of them via the KUBETEST_CONFIGURATION env var
  • capv: add kubetest jobs to replicate k8s e2e tests kubernetes/test-infra#31086
• Compare a run of the jobs with the original ones
  • which cases got skipped but run upstream, ...

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[zhanggbj]

I assume this is still in progress based on the comments above.
/remove-lifecycle rotten

[chrischdi]

I still have to summarise how the state is. We have the periodics running, but they fail on some tests (which was somewhat expected):

• https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-vsphere#periodic-e2e-exp-kk
• https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-vsphere#periodic-e2e-exp-kk-alpha-features
• https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-vsphere#periodic-e2e-exp-kk-serial
• https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-vsphere#periodic-e2e-exp-kk-slow

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale