-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Cloud Provider implementation for AWS #59
Comments
/kind feature |
Has anybody volunteered for this? I meant to attend the SIG meeting today and introduce myself, however prior engagements kept me away. I'd like to volunteer. I'm also happy to work with anybody else to implement an AWS actuator. In the past I've used Terraform to launch an HA Kubernetes cluster and have been running kubernetes in a production environment since 1.0.0. I'm ready to align to a single API to provision clusters and I'm in love with this initiative. Therefore, I do have a few questions about technology choices and how the freedom could be allowed through the API:
Thanks! |
Hi Dale - we had a couple of people starting some work on the AWS provider implementation before but those didn't get sent out as PR (and it's been a while now). So please feel free to pick this up - and thank you for doing it! On your questions. Yes, what each platform provider supports is totally independent from each other. Our goal is that much of the code to support a particular OS can be reused, but we're not at that stage yet. I'd recommend you follow some of the configuration design implemented by @kcoronado for more configurable OS/start up scripts. kubernetes-retired/kube-deploy#664 If you have any questions, please reply here or on Slack. Katie should be able to help with specific questions on her work. As you're not part of the K8s org, I'll assign it to myself so we know that this is being worked on. cc @dragan |
Hi Rodrigo! No problem, I'm happy to help! Thanks for the information and I'll take a look @kcoronado PR. I'm starting on this now! As soon as I have something working, I'll submit a PR to start the feedback process. /cc @rsdcastro |
Now that https://github.com/kubernetes-sigs/cluster-api-provider-aws exists I think this issue should be closed and as @enxebre suggested implementation discussions for an aws provider should happen in the new repo. |
…kerfile Add logger package to build container
Added a quick intro guide to using the clusterctl CLI as well as instructions on getting all the necessary components ready. Resolves kubernetes-sigs#56
From @rsdcastro on January 29, 2018 23:8
Copied from original issue: kubernetes-retired/kube-deploy#541
The text was updated successfully, but these errors were encountered: