Replace kube-up e2e clusters with kops for kubernetes/kubernetes e2e testing

upodroid commented 9 months ago

Enhancement Description

One-line enhancement description (can be used as a release note): Replace kube-up e2e clusters with kops for kubernetes/kubernetes e2e testing
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/pull/4250
Discussion Link: https://docs.google.com/document/d/1ADo44wNhzg71EBaHp-oH2-LV88w7Xw8Xqqh22wPdvoc
Primary contact (assignee): @upodroid
Responsible SIGs: sig-testing, sig-cluster-lifecycle
Enhancement target (which target equals to which milestone):
- Alpha release target (x.y): 1.29
- Beta release target (x.y): 1.30
- Stable release target (x.y): 1.30
[x] Alpha
- [ ] KEP (k/enhancements) update PR(s):
- [ ] Code (k/k) update PR(s):
- [ ] Docs (k/website) update PR(s):

/sig testing /sig cluster-lifecycle /kind feature /stage alpha

This KEP partially supersedes #2464 for cluster e2e jobs. node e2e tests don't use kube-up for testing. Prerequisite for https://github.com/kubernetes/kubernetes/issues/78995

neolit123 commented 9 months ago

the PRs that i saw at test-infra were targeting the gce-gcp test jobs, which means the receiving owner is SIG Clound Provider, with a provider GCP?

/sig cloud-provider
/area provider/gcp

EDIT: please remove if no longer true.

aojea commented 9 months ago

most of current CI jobs depend on the kube-up scripts that uses GCE, so it is a sig testing problem .. in addition, we are diversifying cloud providers and aws is adding credits to run the CI infra, so we want to be able to use one or the other independently too

/sig testing /sig infra

k8s-ci-robot commented 9 months ago

@aojea: The label(s) sig/infra cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/enhancements/issues/4224#issuecomment-1729166741): >most of current CI jobs depend on the kube-up scripts that uses GCE, so it is a sig testing problem .. in addition, we are diversifying cloud providers and aws is adding credits to run the CI infra, so we want to be able to use one or the other independently too > >/sig testing >/sig infra > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

upodroid commented 9 months ago

/sig k8s-infra

npolshakova commented 9 months ago

Hi @upodroid, 1.29 Enhancements lead here! Is this KEP targeting 1.29? If it is, can you make sure the lead-opted-in label is set on the issue so it is correctly tracked by the enhancements project board? Thanks!

BenTheElder commented 8 months ago

/label lead-opted-in

BenTheElder commented 8 months ago

Discussed: We will track this for test-freeze targeted deadlines in 1.29 related to fixing tests that assume kube-up.sh implementation details https://github.com/kubernetes/kubernetes/issues/120989, so it will be "alpha" for 1.29 tentatively, it should not put the release at risk and we'll push for more substantial updates in 1.30.

salehsedghpour commented 6 months ago

/remove-label lead-opted-in

k8s-triage-robot commented 3 months ago

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

BenTheElder commented 3 months ago

/remove-lifecycle stale

we're punting this until cloud provider removal is done to minimize the amount of overlapping work

k8s-triage-robot commented 4 days ago