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

Support Cloud Providers #131

Closed
helayoty opened this issue Apr 13, 2022 · 11 comments
Closed

Support Cloud Providers #131

helayoty opened this issue Apr 13, 2022 · 11 comments

Comments

@helayoty
Copy link
Contributor

As a developer, I want to be able to spin up a managed kubernetes cluster from well-known providers i.e. AKS, ESK, GKE

@vladimirvivien
Copy link
Contributor

@helayoty thanks for the issue.
The framework offers EnvFunc types so that test developers can extend their tests. Regardless, I agree it would be useful to use EnvFuncs to stand up popular providers. The code could be hosted in third-party dir to minimize dependency.

@vladimirvivien
Copy link
Contributor

@helayoty you may be interested in issue #132

@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 Jul 25, 2022
@vladimirvivien
Copy link
Contributor

/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 Aug 3, 2022
@helayoty
Copy link
Contributor Author

@vladimirvivien
Copy link
Contributor

Sweet! @helayoty .
We should revisit this soon to show how easy it is to drive kubetest2 providers from e2e-framework tests.

@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 Nov 28, 2022
@vladimirvivien
Copy link
Contributor

/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 Dec 21, 2022
@vladimirvivien
Copy link
Contributor

This issue should be revisited at a future time. My one concern here is keeping up with the evolution/changes in how each provider stand up their cluster. There is work going on to integrate kubetest2 with the e2e-framework (see #168). This would allow test writers to externalize/delegate cluster deployment to kubetest2.

@vladimirvivien
Copy link
Contributor

Hi @helayoty
Now that the e2e-framework supports running tests with kubetest2, can this be closed ?

@helayoty
Copy link
Contributor Author

@vladimirvivien YES. Thanks for making that happen!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants