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

Cloud Provider implementation for AWS #59

Closed
rsdcastro opened this issue Apr 13, 2018 · 6 comments
Closed

Cloud Provider implementation for AWS #59

rsdcastro opened this issue Apr 13, 2018 · 6 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@rsdcastro
Copy link

From @rsdcastro on January 29, 2018 23:8

Copied from original issue: kubernetes-retired/kube-deploy#541

@rsdcastro rsdcastro added cluster-api-aws kind/feature Categorizes issue or PR as related to a new feature. labels Apr 13, 2018
@rsdcastro
Copy link
Author

/kind feature

@rsdcastro rsdcastro added this to the cluster-api-beta-implementation milestone Apr 13, 2018
@dragan
Copy link

dragan commented Apr 18, 2018

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:

  1. Has there been any discussions on allowing freedom in technology choices? For instance, using CoreOS Container Linux instead of say Ubuntu?
  2. With that freedom, the userdata script will change, are there extension points in regards to allowing different meta config templates? Sorry for any misconceptions with the vernacular, I quickly looked over the codebase and I'm still educating myself.

Thanks!

@rsdcastro
Copy link
Author

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
/assign @rsdcastro

@dragan
Copy link

dragan commented Apr 19, 2018

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

@enxebre
Copy link
Member

enxebre commented Jul 16, 2018

bare bones implementation repo has been proposed by @detiber here #425 We'll next share a starting design doc so we have a common place to collaborate and discuss implementation details cc @csrwng @dgoodwin

@roberthbailey
Copy link
Contributor

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.

chuckha pushed a commit to chuckha/cluster-api that referenced this issue Oct 2, 2019
…kerfile

Add logger package to build container
jayunit100 pushed a commit to jayunit100/cluster-api that referenced this issue Jan 31, 2020
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants