Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kubetest2 CI migration #2464

Open
7 of 8 tasks
amwat opened this issue Feb 8, 2021 · 28 comments
Open
7 of 8 tasks

kubetest2 CI migration #2464

amwat opened this issue Feb 8, 2021 · 28 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@amwat
Copy link
Contributor

amwat commented Feb 8, 2021

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Feb 8, 2021
@spiffxp
Copy link
Member

spiffxp commented Feb 9, 2021

/milestone v1.21

@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Feb 9, 2021
@spiffxp
Copy link
Member

spiffxp commented Feb 9, 2021

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Feb 9, 2021
@spiffxp spiffxp added this to To Triage in sig-testing issues via automation Feb 9, 2021
@spiffxp spiffxp moved this from To Triage to Backlog in sig-testing issues Feb 9, 2021
@spiffxp spiffxp moved this from Backlog to In Progress in sig-testing issues Feb 9, 2021
@annajung annajung added the tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team label Feb 10, 2021
@BenTheElder
Copy link
Member

BenTheElder commented Feb 10, 2021

This will be merged implementable momentarily #2479

@spiffxp
Copy link
Member

spiffxp commented Mar 5, 2021

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

@spiffxp
Copy link
Member

spiffxp commented Sep 20, 2021

Checklist for beta:

  • a guide for migration from kubetest to kubetest2 exists
  • gce jobs have moved to kubetest2 (release-blocking, merge-blocking)
    • ci-kubernetes-e2e-gce-device-plugin-gpu
    • ci-kubernetes-e2e-gce-master-new-gci-kubectl-skew
    • ci-kubernetes-e2e-gci-gce
    • ci-kubernetes-e2e-gci-gce-alpha-features
    • ci-kubernetes-e2e-gci-gce-ingress
    • ci-kubernetes-e2e-gci-gce-reboot
    • ci-kubernetes-e2e-ubuntu-gce-containerd
    • pull-kubernetes-e2e-gce-network-proxy-http-connect
    • pull-kubernetes-e2e-gce-ubuntu-containerd
  • release-blocking/merge-blocking node jobs have corresponding shadows on k/k master
  • release-blocking/merge-blocking scale jobs have corresponding shadows on k/k master
    • ci-kubernetes-e2e-gci-gce-scalability
    • pull-kubernetes-e2e-gce-100-performance

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Nov 8, 2021

Hello @amwat 👋

Checking in once more as we approach 1.23 code freeze at 6:00 pm PST on Tuesday, November 16.

Please ensure the following items are completed:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

As always, we are here to help should questions come up.

Thank you so much! 🙂

@amwat
Copy link
Contributor Author

amwat commented Nov 12, 2021

Thanks @Priyankasaggu11929 , updated the PR description with latest info.

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Nov 13, 2021

Thank you so much for the update @amwat. 🙂

@spiffxp
Copy link
Member

spiffxp commented Nov 24, 2021

@amwat did we complete any of the checklist items to actually graduate to beta? I saw a lot of shadow presubmits added this cycle but I'm less clear whether there are any more blocking jobs using kubetest2 than last release

@amwat
Copy link
Contributor Author

amwat commented Nov 24, 2021

Yeah, all of those are are towards the 3rd beta requirement of having shadow node jobs.

We have an overall community guide for migration at: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/e2e-tests-kubetest2.md#testing-against-an-existing-cluster
I think we can keep adding FAQs for migrating specific types of jobs to this doc, but that probably also extends beyond the limitations of this KEP.

But we have not yet made pull-kubernetes-e2e-gce-kubetest2 blocking (thanks for the reminder!)

Note sure if we want to update the target accordingly then.

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Nov 26, 2021

Hello @amwat, could you help providing a status summary on the checklist, mentioned in one of the above comments here. Want to confirm if all fo the items are checked or if not, what all are still in progress..

Thank you so much! 🙂

@gracenng gracenng added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Jan 9, 2022
@gracenng gracenng removed this from the v1.23 milestone Jan 9, 2022
@SergeyKanzhelev
Copy link
Member

SergeyKanzhelev commented Jan 14, 2022

@amwat what is the status of this? Is there plan to fully transition sig node tests to kubetest2 in 1.24?

@BenTheElder
Copy link
Member

BenTheElder commented Feb 4, 2022

@SergeyKanzhelev amwat moved on before your comment and doesn't work in Kubernetes anymore. I don't know who can take up the remainder yet.

@BenTheElder BenTheElder moved this from In Progress to Help Wanted in sig-testing issues Feb 4, 2022
@BenTheElder BenTheElder added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Feb 4, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented May 5, 2022

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

@k8s-ci-robot k8s-ci-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels May 5, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Jun 4, 2022

The Kubernetes project currently lacks enough active 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 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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 4, 2022
@Namanl2001
Copy link
Member

Namanl2001 commented Jun 4, 2022

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 4, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 2, 2022

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2022
@cpanato
Copy link
Member

cpanato commented Sep 2, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2022
@cpanato
Copy link
Member

cpanato commented Sep 2, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
sig-testing issues
  
Help Wanted
Development

No branches or pull requests