Terraform module to create Amazon Elastic Kubernetes (EKS) resources πΊπ¦
APACHE-2.0 License
Bot releases are hidden (Show)
Published by antonbabenko almost 2 years ago
Please consult the examples
directory for reference example configurations. If you find a bug, please open an issue with supporting configuration to reproduce.
cluster_id
output used to output the name of the cluster. This is due to the fact that the cluster name is a unique constraint and therefore its set as the unique identifier within Terraform's state map. However, starting with local EKS clusters created on Outposts, there is now an attribute returned from the aws eks create-cluster
API named id
. The cluster_id
has been updated to return this value which means that for current, standard EKS clusters created in the AWS cloud, no value will be returned (at the time of this writing) for cluster_id
and only local EKS clusters on Outposts will return a value that looks like a UUID/GUID. Users should switch all instances of cluster_id
to use cluster_name
before upgrading to v19. Reference
var.iam_role_additional_policies
(one for each of the following: cluster IAM role, EKS managed node group IAM role, self-managed node group IAM role, and Fargate Profile IAM role) accepted a list of strings. This worked well for policies that already existed but failed for policies being created at the same time as the cluster due to the well known issue of unkown values used in a for_each
loop. To rectify this issue in v19.x
, two changes were made:
var.iam_role_additional_policies
was changed from type list(string)
to type map(string)
-> this is a breaking change. More information on managing this change can be found below, under Terraform State Moves
try()
with lookup()
. More details on why can be found here
ClusterName
tag and the event rule name is now a prefix. This guarantees that users can have multiple instances of Karpenter withe their respective event rules/SQS queue without name collisions, while also still being able to identify which queues and event rules belong to which cluster.Please see the UPGRADE-19.0.md for full details on changes and upgrade path.