-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Export to Terraform #181
Comments
@mikemorris thanks! There are a couple of ways this could be achieved, but I'd like to understand the use-cases better. Short term, the easiest way would be to use CloudFormation+Terraform, i.e. However, I would like to make it clear, that long term, the plan is provide to Cluster API support (#19 & #20), which essentially means that instead of |
For one, I think that eksctl is a great starting point for clusters with a lot of configurable options (like installing the WeaveNet cni). For multi-cloud provider setups, terraform is fantastic - so if eksctl could output terraform scripts to be included in a multi-cloud provider project I think we get the best of both worlds. |
@TigerC10 thank you, this is quite helpful. Are there any other use-case? |
My use-case is similar, although our infra is primarily on AWS - eksctl is a great quick setup tool, but we try to follow the "configuration as code" approach, using Terraform to manage all our infrastructure and tracking changes through a git repo (hopefully getting to a "GitOps" flow where changes are deployed by commiting and merging code eventually), would be great to at least be able to output the initial cluster config as Terraform files. |
Looking eksctl to terraform config file |
there's this project also written in go that supports exporting some AWS TF resources, but not EKS yet unfortunately. |
Closing in favour of #1094. |
Update driver manifest files
It would be great to offer an option to export a cluster configuration to be managed in Terraform, similar to the
--target=terraform
functionality in kops.Breaking this out from initial discussion in #132 (comment)
/cc @richardcase @errordeveloper
The text was updated successfully, but these errors were encountered: