Skip to content
This repository has been archived by the owner on May 22, 2020. It is now read-only.

Support multiple providers for cluster bootstrapping #524

Closed
rsdcastro opened this issue Jan 29, 2018 · 4 comments
Closed

Support multiple providers for cluster bootstrapping #524

rsdcastro opened this issue Jan 29, 2018 · 4 comments
Labels
cluster-api
Milestone
cluster-api-beta-...

Comments

@rsdcastro
Copy link

Currently only GCP is supported. This item is about - more easily - supporting other providers when bootstrapping a cluster.
@rsdcastro
Copy link
Author

This could include defining an interface and/or documentation. The goal is that anyone implementing a new provider knows that they would need to implement the bootstrapping story as well (assuming we keep the current implementation of starting an instance to install the controller as default). @krousey @karan

@karan
Copy link
Contributor

karan commented Jan 31, 2018

Related #550

@rsdcastro rsdcastro added this to the cluster-api-alpha milestone Feb 2, 2018
@rsdcastro
Copy link
Author

As supporting more providers is out of scope for alpha, moving it to beta.

@rsdcastro rsdcastro modified the milestones: cluster-api-alpha, cluster-api-beta Feb 12, 2018
@rsdcastro rsdcastro mentioned this issue Apr 12, 2018
Closed
@rsdcastro
Copy link
Author

This issue was moved to kubernetes-sigs/cluster-api#17

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
cluster-api
Projects
None yet
Milestone
cluster-api-beta-implementation
Development

No branches or pull requests
2 participants
@rsdcastro @karan