Bump terraform-aws-modules/eks/aws from 18.26.6 to 19.0.4

[dependabot]

Bumps terraform-aws-modules/eks/aws from 18.26.6 to 19.0.4.

Release notes

Sourced from terraform-aws-modules/eks/aws's releases.

v19.0.4

19.0.4 (2022-12-07)

Bug Fixes

• Ensure that custom KMS key is not created if encryption is not enabled, support computed values in cluster name (#2328) (b83f6d9)

v19.0.3

19.0.3 (2022-12-07)

Bug Fixes

• Invalid value for "replace" parameter: argument must not be null. (#2322) (9adc475)

v19.0.2

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

19.0.1 (2022-12-06)

Bug Fixes

• Call to lookup() closed too early, breaks sg rule creation in cluster sg if custom source sg is defined. (#2319) (7bc4a27)

v19.0.0

19.0.0 (2022-12-05)

⚠ 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

• The 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
• Minimum supported version of Terraform AWS provider updated to v4.45 to support latest features provided via the resources utilized.
• Minimum supported version of Terraform updated to v1.0
• Individual security group created per EKS managed node group or self managed node group has been removed. This configuration went mostly un-used and would often cause confusion ("Why is there an empty security group attached to my nodes?"). This functionality can easily be replicated by user's providing one or more externally created security groups to attach to nodes launched from the node group.
• Previously, 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:
  1. 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
  2. The logic used in the root module for this variable was changed to replace the use of try() with lookup(). More details on why can be found here
• The cluster name has been removed from the Karpenter module event rule names. Due to the use of long cluster names appending to the provided naming scheme, the cluster name has moved to a 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.

... (truncated)

Changelog

Sourced from terraform-aws-modules/eks/aws's changelog.

19.0.4 (2022-12-07)

Bug Fixes

• Ensure that custom KMS key is not created if encryption is not enabled, support computed values in cluster name (#2328) (b83f6d9)

19.0.3 (2022-12-07)

Bug Fixes

• Invalid value for "replace" parameter: argument must not be null. (#2322) (9adc475)

19.0.2 (2022-12-06)

Bug Fixes

• public_access_cidrs require a value even if public endpoint is disabled (#2320) (3f6d915)

19.0.1 (2022-12-06)

Bug Fixes

• Call to lookup() closed too early, breaks sg rule creation in cluster sg if custom source sg is defined. (#2319) (7bc4a27)

19.0.0 (2022-12-05)

⚠ BREAKING CHANGES

• Add support for Outposts, remove node security group, add support for addon preserve and most_recent configurations (#2250)

Features

• Add support for Outposts, remove node security group, add support for addon preserve and most_recent configurations (#2250) (b2e97ca)

18.31.2 (2022-11-23)

Bug Fixes

• Ensure that var.create is tied to all resources correctly (#2308) (3fb28b3)

18.31.1 (2022-11-22)

Bug Fixes

... (truncated)

Commits

• 7124d76 chore(release): version 19.0.4 [skip ci]
• b83f6d9 fix: Ensure that custom KMS key is not created if encryption is not enabled, ...
• c0423ef chore(release): version 19.0.3 [skip ci]
• 9adc475 fix: Invalid value for "replace" parameter: argument must not be null. (#2322)
• f09a643 chore(release): version 19.0.2 [skip ci]
• 3f6d915 fix: public_access_cidrs require a value even if public endpoint is disable...
• 2def94e chore(release): version 19.0.1 [skip ci]
• 7bc4a27 fix: Call to lookup() closed too early, breaks sg rule creation in cluster sg...
• 4bb83e0 chore(release): version 19.0.0 [skip ci]
• b2e97ca feat!: Add support for Outposts, remove node security group, add support for ...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #191.