Eksctl: Support Terraform recipes as advanced cluster options

[gjmveloso]

Before creating a feature request, please search existing feature requests to see if you find a similar one. If there is a similar feature request please up-vote it and/or add your comments to it instead

Why do you want this feature?
Customers may be interested on keep using their own Terraform recipes to fine-grained tuning on what to deploy regarding their EKS clusters and dependencies like VPCs, databases, etc.

What feature/behavior/change do you want?
eksctl working with custom Terraform recipe instead of only accepting CloudFormation templates

Do not hesitate, when appropriate, to share the exact commands or API you would like, and/or to share a diagram (e.g.: asciiflow.com): "a picture is worth a thousand words".

[errordeveloper]

After some consideration, I've opened #1094 to discuss Terraform use-cases more broadly.

If we create a terraform provider, I think it will help with most of your concerns.

For example, you would be able to manage whatever you need with Terraform, and reference those resources in eksctl_cluster resource.

Here is an example of what it could look like:

resource "aws_security_group" "eks_cluster" { ... }
resource "aws_iam_policy" "eks_nodegroup" { ... }

resource "eksctl_cluster" "cluster-1" {
  vpc {
    securityGroup = "${aws_security_group.eks_cluster.id}"
  }
  nodeGroups = [{
   name = "ng-1"
   attachPolicyARNs = [ "${aws_iam_policy.eks_nodegroup.arn}" ]
  }]
}

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.