Skip to content
This repository was archived by the owner on Feb 10, 2026. It is now read-only.

v1.303.0

Choose a tag to compare

View all tags
@cloudpossebot cloudpossebot released this 01 Sep 03:57
· 301 commits to refs/heads/main since this release
1.303.0
e3f8c13
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
[eks/cluster] Bug fixes for add-ons Nuru (@Nuru) (#852)

what and why

Changes to eks/cluster:

  • Timeouts for Add-Ons are now honored (they were being ignored)
  • If you supply a service account role ARN for an Add-On, it will be used, and
    no new role will be created. Previously it was used, but the component created
    a new role anyway.
  • The EKS EFS controller add-on cannot be deployed to Fargate, and enabling it
    along with deploy_addons_to_fargate will no longer attempt to deploy EFS
    to Fargate. Note that this means to use the EFS Add-On, you must create
    a managed node group. Track the status of this feature with this issue.
  • If you are using an old VPC component that does not supply az_private_subnets_map,
    this module will now use the older the private_subnet_ids output.
  • The EKS Add-Ons now have an optional "enabled" flag (defaults to true) so
    that you can selectively disable them in a stack where the inherited configuration
    has them enabled.

references

Contributors

Nuru
Assets 2
Loading