-
Notifications
You must be signed in to change notification settings - Fork 98
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
Comments
@helayoty thanks for the issue. |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Sweet! @helayoty . |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
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. |
Hi @helayoty |
@vladimirvivien YES. Thanks for making that happen! |
As a developer, I want to be able to spin up a managed kubernetes cluster from well-known providers i.e. AKS, ESK, GKE
The text was updated successfully, but these errors were encountered: