kubetest2 CI migration

[amwat]

Enhancement Description

• One-line enhancement description (can be used as a release note): Migration of presubmit-blocking and release-blocking end-to-end CI jobs to kubetest2

• Kubernetes Enhancement Proposal: https://git.k8s.io/enhancements/keps/sig-testing/2464-kubetest2-ci-migration

• Discussion Link:

• Primary contact (assignee): @amwat

• Responsible SIGs: SIG-Testing, SIG-Release

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): 1.21
  • Beta release target (x.y): 1.23
  • Stable release target (x.y): 1.24

• Alpha

  • KEP (k/enhancements) update PR(s): Add KEP 2464: Kubetest2 CI migration #2465, Move Kubetest2 CI migration to implementable #2479
  • Code (k/k) update PR(s): N/A
  • Docs (k/website) update PR(s): N/A

• Beta

  • KEP (k/enhancements) update PR(s): keps/sig-testing: propose v1.23 graduations #2871
  • Code (k/k) update PR(s): enabling IMAGE_CONFIG_DIR in make file for testing purposes kubernetes#106013 , adding --ssh-key and --ssh-user for kubetest2 kubernetes#105637
  • Docs (k/website) update(s): N/A

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

This will be in: https://github.com/kubernetes/enhancements/tree/master/keps/sig-testing/2464-kubetest2-ci-migration

/assign
/sig testing
/sig release

[spiffxp]

/milestone v1.21

[spiffxp]

/priority important-soon

[BenTheElder]

This will be merged implementable momentarily #2479

[spiffxp]

I would bucket this KEP under process when #2311 is completed

[Namanl2001]

/remove-lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[cpanato]

/remove-lifecycle stale

[cpanato]

i will take a look on this, maybe just need some quick recap :)
cc @BenTheElder

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

[cpanato]

@BenTheElder gently ping here :)

[BenTheElder]

@cpanato I don't have a lot to add unfortunately, the last I saw we were blocked on getting SIG Node input to migrate node_e2e support, and the large lift to port existing job configs otherwise, in theory the tooling works for kube-up/kOps e2e tests today and it is used for kOps and some kube-up.sh/GCE jobs.

[BenTheElder]

I stepped down from kubetest/kubetest2, it became one too many projects to maintain with the high focus on infra costs. I'm no longer an approver in kubetest2.

cc @aojea @pohly @cjwagner @alvaroaleman (the rest of our SIG TLs)

[aojea]

If nobody is going to work on this we should close the issue,no?

is not really a feature, it seems to track only the effort to do it

[BenTheElder]

@aojea #2464 (comment) ?

otherwise yes

[vaibhav2107]

/remove-lifecycle stale

[cpanato]

agree @aojea

[upodroid]

/assign

Can we track this for 1.29?

Core Goals:

• Run the node e2e tests using kubetest2 and replace the old kubetest1 tests that are part of master-blocking/informing
• Run the GCE Kubernetes e2e tests against amd64 on kubetest2 and replace the old kubetest1 tests that are part of master-blocking/informing
• Roll out the EC2 node tests using kubetest2

Stretch Goals:

• arm64 cluster e2e tests on GCE. Initial work [WIP] Fix cluster scripts to support arm64 GCE tests kubernetes#120144

@dims

[dims]

@upodroid sounds good to me :)