chore(deps): update terraform github.com/terraform-aws-modules/terraform-aws-eks to v20 #20
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v18.2.0
->v20.26.0
Release Notes
terraform-aws-modules/terraform-aws-eks (github.com/terraform-aws-modules/terraform-aws-eks)
v20.26.0
Compare Source
Features
desired_capacity_type
(nameddesired_size_type
) on self-managed node group (#3166) (6974a5e)v20.25.0
Compare Source
Features
Bug Fixes
v20.24.3
Compare Source
Bug Fixes
primary_ipv6
parameter to self-managed-node-group (#3169) (fef6555)v20.24.2
Compare Source
Bug Fixes
inline_policy
from cluster role (#3163) (8b90872)v20.24.1
Compare Source
Bug Fixes
v20.24.0
Compare Source
Features
v20.23.0
Compare Source
Features
v20.22.1
Compare Source
Bug Fixes
v20.22.0
Compare Source
Features
v20.21.0
Compare Source
Features
upgrade_policy
(#3112) (e12ab7a)v20.20.0
Compare Source
Features
v20.19.0
Compare Source
Features
primary_ipv6
argument to the AWS provider. (#3098) (e1bb8b6)v20.18.0
Compare Source
Features
bootstrap_self_managed_addons
(#3099) (af88e7d)v20.17.2
Compare Source
Bug Fixes
v20.17.1
Compare Source
Bug Fixes
aws_iam_session_context
data source only when required (#3058) (f02df92)v20.17.0
Compare Source
Features
v20.16.0
Compare Source
Features
v20.15.0
Compare Source
Features
v20.14.0
Compare Source
Features
ami_type
and not viaplatform
which is unable to distinquish between the number of variants supported today (#3068) (ef657bf)v20.13.1
Compare Source
Bug Fixes
bootstrap_cluster_creator_admin_permissions
and not all ofaccess_config
(#3056) (1e31929)v20.13.0
Compare Source
Features
1.30
, do not use the cluster OIDC issuer URL by default in the identity provider config (#3055) (00f076a)v20.12.0
Compare Source
Features
v20.11.1
Compare Source
Bug Fixes
bootstrap_cluster_creator_admin_permissions
which is disabled by default (#3042) (c65d308)v20.11.0
Compare Source
Features
SourceArn
condition to Fargate profile trust policy (#3039) (a070d7b)v20.10.0
Compare Source
Features
v20.9.0
Compare Source
Features
ami_type
to self-managed node group; allow usingami_type
only (#3030) (74d3918)v20.8.5
Compare Source
Bug Fixes
v20.8.4
Compare Source
Bug Fixes
v20.8.3
Compare Source
Bug Fixes
v20.8.2
Compare Source
Bug Fixes
ip_family
value is provided to guarantee a CNI policy is attached to nodes (#2967) (29dcca3)v20.8.1
Compare Source
Bug Fixes
v20.8.0
Compare Source
Features
toset()
with static keys for node IAM role policy attachment (#2962) (57f5130)v20.7.0
Compare Source
Features
v20.6.0
Compare Source
Features
v20.5.3
Compare Source
Bug Fixes
AL2023_*
AMI types; ensure AL2023 user data receives cluster service CIDR (#2960) (dfe4114)v20.5.2
Compare Source
Bug Fixes
launch_template_tags
on the launch template (#2957) (0ed32d7)v20.5.1
Compare Source
Bug Fixes
v20.5.0
Compare Source
Features
nodeadm
user data (#2942) (7c99bb1)v20.4.0
Compare Source
Features
v20.3.0
Compare Source
Features
v20.2.2
Compare Source
20.2.2 (2024-02-21)
Bug Fixes
amazonaws.com
(#2941) (081c762)v20.2.1
Compare Source
20.2.1 (2024-02-08)
Bug Fixes
enable_spot_termination = false
should not result in an error (#2907) (671fc6e)v20.2.0
Compare Source
Features
v20.1.1
Compare Source
20.1.1 (2024-02-06)
Bug Fixes
kubernetes_groups
default value tonull
(#2897) (1e32e6a)v20.1.0
Compare Source
Features
access_policy_associations
(#2904) (0d2a4c2)v20.0.1
Compare Source
20.0.1 (2024-02-03)
Bug Fixes
v20.0.0
Compare Source
⚠ BREAKING CHANGES
aws-auth
configmap with EKS cluster access entry (#2858)See the UPGRADE-20.0.md guide for further details on the changes and guidance for upgrading
List of backwards incompatible changes
v5.34
v1.3
to support Terraform statemoved
blocks as well as other advanced featuresresolve_conflicts
argument within thecluster_addons
configuration has been replaced withresolve_conflicts_on_create
andresolve_conflicts_on_delete
now thatresolve_conflicts
is deprecatedpreserve
argument ofcluster_addons
is now set totrue
. This has shown to be useful for users deprovisioning clusters while avoiding the situation where the CNI is deleted too early and causes resources to be left orphaned resulting in conflicts.irsa
naming convention has been removed, along with an update to the Karpenter controller IAM policy to align with Karpenter'sv1beta1
/v0.32
changes. Instead of referring to the role asirsa
orpod_identity
, its simply just an IAM role used by the Karpenter controller and there is support for use with either IRSA and/or Pod Identity (default) at this timeaws-auth
ConfigMap resources have been moved to a standalone sub-module. This removes the Kubernetes provider requirement from the main module and allows for theaws-auth
ConfigMap to be managed independently of the main module. This sub-module will be removed entirely in the next major release.API_AND_CONFIG_MAP
. This is a one way change if applied; if you wish to useCONFIG_MAP
, you will need to setauthentication_mode = "CONFIG_MAP"
explicitly when upgrading.spot_interrupt
updated to correct mis-spelling (wasspot_interupt
). This will cause the rule to be replacedAdditional changes
Added
bootstrap_cluster_creator_admin_permissions
setting on the control plane has been hardcoded tofalse
since this operation is a one time operation only at cluster creation per the EKS API. Instead, users can enable/disableenable_cluster_creator_admin_permissions
at any time to achieve the same functionality. This takes the identity that Terraform is using to make API calls and maps it into a cluster admin via an access entry. For users on existing clusters, you will need to remove the default cluster administrator that was created by EKS prior to the cluster access entry APIs - see the sectionRemoving the default cluster administrator
for more details.instance_maintenance_policy
and have addedmax_healthy_percentage
,scale_in_protected_instances
, andstandby_instances
arguments to theinstance_refresh.preferences
blockModified
sts:AssumeRole
permissions by services, the use of dynamically looking up the DNS suffix has been replaced with the static value ofamazonaws.com
. This does not appear to change by partition and instead requires users to set this manually for non-commercial regions.kms_key_enable_default_policy
has changed fromfalse
totrue
to align with the default behavior of theaws_kms_key
resourcecreate_instance_profile
has changed fromtrue
tofalse
to align with the changes in Karpenter v0.32create_instance_profile
default value has changed fromtrue
tofalse
. Starting with Karpenterv0.32.0
, Karpenter accepts an IAM role and creates the EC2 instance profile used by the nodesRemoved
complete
example has been removed due to its redundancy with the other examplesv19.21.0
Compare Source
Features
v19.20.0
Compare Source
Features
v19.19.1
Compare Source
19.19.1 (2023-11-10)
Bug Fixes
v19.19.0
Compare Source
Features
create_kms_key = false
(#2804) (0732bea)v19.18.0
Compare Source
Features
v19.17.4
Compare Source
19.17.4 (2023-10-30)
Bug Fixes
v19.17.3
Compare Source
19.17.3 (2023-10-30)
Bug Fixes
license_configuration_arn
(#2796) (bd4bda2)v19.17.2
Compare Source
19.17.2 (2023-10-10)
Bug Fixes
v19.17.1
Compare Source
19.17.1 (2023-10-06)
Bug Fixes
v19.17.0
Compare Source
Features
allowed_instance_types
on self-managed nodegroup ASG (#2757) (feee18d)v19.16.0
Compare Source
Features
node_iam_role_arns
local variable to check for Windows platform on EKS managed nodegroups (#2477) (adb47f4)v19.15.4
Compare Source
19.15.4 (2023-07-27)
Bug Fixes
coalesce
when desired default value is notnull
(#2696) (c86f8d4)v19.15.3
Compare Source
19.15.3 (2023-06-09)
Bug Fixes
v19.15.2
Compare Source
19.15.2 (2023-05-30)
Bug Fixes
isra_tag_values
can be tried before defaulting tocluster_name
on Karpenter module (#2631) (6c56e2a)v19.15.1
Compare Source
19.15.1 (2023-05-24)
Bug Fixes
role_last_used
(#2629) (e23139a)v19.15.0
Compare Source
Features
v19.14.0
Compare Source
Features
v19.13.1
Compare Source
19.13.1 (2023-04-18)
Bug Fixes
v19.13.0
Compare Source
Features
v19.12.0
Compare Source
Features
v19.11.0
Compare Source
Features
v19.10.3
Compare Source
19.10.3 (2023-03-23)
Bug Fixes
aws_eks_addons.before_compute
to thecluster_addons
output (#2533) (f977d83)v19.10.2
Compare Source
19.10.2 (2023-03-23)
Bug Fixes
v19.10.1
Compare Source
19.10.1 (2023-03-17)
Bug Fixes
v19.10.0
Compare Source
Features
v19.9.0
Compare Source
Features
v19.8.0
Compare Source
Features
v19.7.0
Compare Source
Features
v19.6.0
Compare Source
Features
v19.5.1
Compare Source
19.5.1 (2023-01-05)
Bug Fixes
v19.5.0
Compare Source
Features
aws-auth
ConfigMap (#2380) (5015b42)v19.4.3
Compare Source
19.4.3 (2023-01-05)
Bug Fixes
v19.4.2
Compare Source
19.4.2 (2022-12-20)
Bug Fixes
v19.4.1
Compare Source
19.4.1 (2022-12-20)
Bug Fixes
eks_managed_*
toself_managed_*
fortag_specification
argument (#2364) (df7c57c)v19.4.0
Compare Source
Features
v19.3.1
Compare Source
19.3.1 (2022-12-18)
Bug Fixes
v19.3.0
Compare Source
Features
metrics-server
to recommended rules (#2353) (5a270b7)v19.2.0
Compare Source
Features
tag_specifications
on launch templates (#2352) (0751a0c)v19.1.1
Compare Source
19.1.1 (2022-12-17)
Bug Fixes
assumed_role
(#2347) (71b8eca)v19.1.0
Compare Source
Features
configuration_values
(#2345) (3b62f6c)v19.0.4
Compare Source
19.0.4 (2022-12-07)
Bug Fixes
v19.0.3
Compare Source
19.0.3 (2022-12-07)
Bug Fixes
v19.0.2
Compare Source
19.0.2 (2022-12-06)
Bug Fixes
public_access_cidrs
require a value even if public endpoint is disabled (#2320) (3f6d915)v19.0.1
Compare Source
19.0.1 (2022-12-06)
Bug Fixes
v19.0.0
Compare Source
⚠ BREAKING CHANGES (#2250) (b2e97ca)
Please consult the
examples
directory for reference example configurations. If you find a bug, please open an issue with supporting configuration to reproduce.List of backwards incompatible changes
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 theaws eks create-cluster
API namedid
. Thecluster_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) forcluster_id
and only local EKS clusters on Outposts will return a value that looks like a UUID/GUID. Users should switch all instances ofcluster_id
to usecluster_name
before upgrading to v19. Referencevar.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 afor_each
loop. To rectify this issue inv19.x
, two changes were made:var.iam_role_additional_policies
was changed from typelist(string)
to typemap(string)
-> this is a breaking change. More information on managing this change can be found below, underTerraform State Moves
try()
withlookup()
. More details on why can be found hereClusterName
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.
v18.31.2
Compare Source
[18.31.2](https://togithub.com/terraform-aws-modu
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.