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.

Sign up for GitHub

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

Jump to bottom

kubetest2 CI migration #2464

Open
7 of 8 tasks
Tracked by #29946
amwat opened this issue Feb 8, 2021 · 38 comments
Open
7 of 8 tasks
Tracked by #29946

kubetest2 CI migration #2464

amwat opened this issue Feb 8, 2021 · 38 comments
Assignees
@upodroid
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
Projects
sig-testing issues

Comments

@amwat
Copy link
Contributor

amwat commented Feb 8, 2021 •
edited

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
@amwat amwat mentioned this issue Feb 8, 2021
Merged
@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
@amwat amwat mentioned this issue Feb 9, 2021
Merged
@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

This will be merged implementable momentarily #2479

This was referenced Feb 25, 2021
Merged
Merged
Closed
Merged
Closed
Merged
Closed
@amwat amwat mentioned this issue Mar 5, 2021
Closed
@spiffxp
Copy link
Member

spiffxp commented Mar 5, 2021

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

This was referenced Mar 5, 2021
Merged
Merged
Merged
Closed
Closed
Closed
Closed
@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

/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

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

@k8s-triage-robot
Copy link

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

@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 Feb 8, 2023
@cpanato
Copy link
Member

cpanato commented May 11, 2023

@BenTheElder gently ping here :)

@BenTheElder
Copy link
Member

@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
Copy link
Member

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
Copy link
Member

aojea commented May 12, 2023

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
Copy link
Member

@aojea #2464 (comment) ?

otherwise yes

@Atharva-Shinde Atharva-Shinde removed the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label May 14, 2023
@vaibhav2107
Copy link
Member

/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 May 26, 2023
@cpanato
Copy link
Member

cpanato commented May 30, 2023

agree @aojea

This was referenced Jun 27, 2023
Closed
Closed
@upodroid upodroid mentioned this issue Jul 25, 2023
Merged
This was referenced Aug 14, 2023
Open
Closed
@upodroid
Copy link
Member

upodroid commented Aug 24, 2023 •
edited

/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:

@dims

@dims
Copy link
Member

dims commented Aug 24, 2023

@upodroid sounds good to me :)

@upodroid upodroid mentioned this issue Sep 12, 2023
Closed
@upodroid upodroid mentioned this issue Sep 20, 2023
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@upodroid upodroid

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
Projects
sig-testing issues
  
Help Wanted
Milestone
No milestone
Development

No branches or pull requests