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

Cluster API CLI #19

Closed
errordeveloper opened this issue Jun 4, 2018 · 4 comments
Closed

Cluster API CLI #19

errordeveloper opened this issue Jun 4, 2018 · 4 comments
Assignees
Labels
help wanted Extra attention is needed priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases

Comments

@errordeveloper
Copy link
Contributor

errordeveloper commented Jun 4, 2018

We would like to implement Cluster API. One of the modes in which one can use Cluster API would be eksctl apply -f cluster.yaml, this would let users create and update clusters using a declarative format of a Cluster API object.
Another mode of using Cluster API would be via a controller running in a management cluster (#20).

@errordeveloper
Copy link
Contributor Author

errordeveloper commented Jan 4, 2019

What needs to be done here?

This issue was set out for 0.3.0 and not 0.2.0, and that is still the plan, however that doesn't stop us from laying the ground work and introducing experimental functionality (hence #381 is about go into 0.1.17).

  • eksctl create cluster -f <configFile>Create cluster via config file #381 (landed in 0.1.17)
  • eksctl create nodegroup -f <configFile> – Adding config file option for create nodegroup #553 (landed in 0.1.23)
  • eksctl create -f <configFile>
  • eksctl get cluster/nodegroup -o yaml|json (we have somewhat ad-hoc format for these, should use the API instead)
  • eksctl get/delete cluster -f <configFile> (delete make it easy to delete cluster with a config file  #504)
  • eksctl get/delete nodegroup -f <configFile>
  • eksctl get/delete -f <configFile>
  • eksctl utils upgrade-{cluster,nodegroup} -f <configFile> (in case we may need it as a temporary solution for upgrades, before we can implement fully idempotent eksctl apply)
  • eksctl apply -f <configFile>

We will evolve the API itself in parallel, the above list is just to illustrate the functionality at the high-level.

@mumoshu
Copy link
Contributor

mumoshu commented Nov 19, 2019

@errordeveloper It seems like we have eksctl upgrade nodegroup since #1566, only for upgrading k8s versions.

@michaelbeaumont
Copy link
Contributor

michaelbeaumont commented Oct 13, 2020

We'd love to hear users requirements/interest in this issue. Keep in mind, there's already the AWS provider. We also have an issue for declarative apply #462 #2774
This issue would cover expressing an EKS configuration as a collection of CAPI resources

@michaelbeaumont
Copy link
Contributor

Closing for now

torredil pushed a commit to torredil/eksctl that referenced this issue May 20, 2022
Add license scan report and status
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases
Projects
None yet
Development

No branches or pull requests

4 participants