This is a complete rework of the upstream community EKS module: https://github.com/terraform-aws-modules/terraform-aws-eks

⚠️ Only Terraform >= 0.12 will be supported. Based on v9.0.x of the upstream module.

The interface to the module is the same similar, but it attempts to be more flexible by allowing users to create and use components separately by splitting out sub-modules for:

• EKS Control Plane
• EKS Worker Groups
• EKS Managed Node Groups
• aws-auth Configuration

The submodules are designed to be used as individual modules to help the user perform actions in between creating the control plane and creating workers and nodes (Custom CNI Configuration).

By breaking out separate sub modules we create a clearer separation of concerns and reduce tight coupling of control plane and worker nodes whilst maintaining the same interface for seamless migration to this module. The interface has become an example implementation of the sub-modules.

There are some core implementation changes from the original eks module:

1. Launch Configuration support removed in favour of Launch Template driven worker_groups sub-module. They're doing the same things with no benefit to supporting both LC's and LT's (to my current knowledge). worker_groups_launch_template has been dropped and worker_groups now creates LT's.

2. Simplified code through merging defaults. A pattern I saw in the node_groups sub-module which I really liked. Merging the defaults local, defaults variable and and map values:

   # Merge defaults and per-group values to make code cleaner
   worker_groups_expanded = { for k, v in var.worker_groups : k => merge(
     local.worker_groups_defaults,
     var.worker_groups_defaults,
     v,
   ) if var.create_eks }
   

   It means that code moves from this:

   enabled_metrics = lookup(
     var.worker_groups[count.index],
     "enabled_metrics",
     local.workers_group_defaults["enabled_metrics"]
   )
   

   To this:

   enabled_metrics = each.value["enabled_metrics"]
   

3. Enabling a map of maps for worker_groups. By passing in a map of maps we can add and remove worker_groups without affecting the existing resources. A list of maps still works with all of the issues when removing objects from the list.

   With the sub-module approach, there's nothing stopping a user from using a module instance per worker_group further isolating the data structures in the state file.

No provider.

[
  "secrets"
]

[
  "0.0.0.0/0"
]

list(object({
    rolearn  = string
    username = string
    groups   = list(string)
  }))

list(object({
    userarn  = string
    username = string
    groups   = list(string)
  }))