Leveraging eks-blueprints/kubernetes-addons without eks-blueprints eks module

[nitrocode]

https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/0529549fa2f4b07f65c199c2573b81b2e979aa56/examples/eks-cluster-with-new-vpc/main.tf#L[…]1

This example shows soooo many kubernetes addons to use with simple switches and all we’d need to do is feed in the eks cluster id

I know we spoke about eks blueprints before but I don’t know if we spoke specifically of the kubenetes-addons submodule in conjunction with our eks module

[osterman]

It sounds interesting. I just wish there was some way we could do a catalog-based approach without needing to define a hundred components that wrap their modules.

[nitrocode]

Couldn't we just create a component that uses the kubernetes addons submodule that they provide? Then all we would have to do is expose each of those inputs to variables.tf and then it would be available through the catalog.

components:
  terraform:
    eks/cluster:
      vars:
        enabled: true
        name: eks

    eks/cluster-addons:
      metadata:
        component: eks/cluster-addons
      vars:
        enabled: true
        eks_component_name: eks/cluster

        enable_aws_load_balancer_controller: true
        enable_metrics_server: true
        enable_aws_cloudwatch_metrics: true
        enable_kubecost: true
        enable_gatekeeper: true
        # ...etc

[osterman]

Ok, so also add a component.yaml example, since that's the missing piece.

[nitrocode]

The component.yaml file that vendors a component from terraform-aws-component? That would be pretty much the same as all the other component.yaml files. Only difference would be the name of the component to download. Maybe I'm misunderstanding you. Could you reword your request?

[osterman]

Yes, let's do this, but I don't think we'll use it to replace anything we have existing support for.

[osterman]

@nitrocode to create a prototype component in cloudposse/terraform-aws-components

[ChrisMcKee]

Worth noting their plan for v5 changes it all

[nitrocode]

Apologies I didn't get a chance to implement this before.

As ChrisMcKee already mentioned, it looks like eks-blueprints has been broken out into a few more modules

1. terraform-aws-eks-blueprint-addon -
   (Note the singular form) Terraform module which can provision an addon using the Terraform
   helm_release resource in addition to an IAM role for service account (IRSA).
2. terraform-aws-eks-blueprint-addons -
   (Note the plural form) Terraform module which can provision multiple addons; both EKS addons
   using the aws_eks_addon resource as well as Helm chart based addons using the
   terraform-aws-eks-blueprint-addon module.
3. terraform-aws-eks-blueprints-teams -
   Terraform module that creates Kubernetes multi-tenancy resources and configurations, allowing both
   administrators and application developers to access only the resources which they are responsible for.

It would be nice to create a component for all of these.

1. Would be good for addons that aren't supported by the plural module
2. This plural module supports a lot of foundational charts out of the box which is great for common use-cases
3. This is awesome for least privileges for teams that require access to eks