v4.0.0 Major breaking changes
Major breaking changes. Review the migration guide for guidance about upgrading.
In this version we fulfill the promise of managing EKS access via AWS APIs rather than via the various hacks we employed to make it possible to manage access via the aws-auth
ConfigMap. As a result, all references to the Kubernetes Terraform AWS provider have been removed, requiring manual intervention for upgrading from previous versions.
We also removed Security Group and other inputs deprecated in version 2.
We believe the final result is much cleaner, more reliable, and more stable than earlier versions, but the upgrade is unfortunately non-trivial. Please allow yourself sufficient time to read the migration guide before upgrading.
Use AWS API for EKS authentication and authorization @Nuru (#206)
Major Breaking Changes
[!WARNING]
This release has major breaking changes and requires significant manual intervention
to upgrade existing clusters. Read the migration document
for more details.
what
- Use the AWS API to manage EKS access controls instead of the
aws-auth
ConfigMap - Remove support for creating an extra security group, deprecated in v2
- Add IPv6 service CIDR output
- Update test framework to
go
v1.21, Kubernetes 1.29, etc.
why
- Remove a large number of bugs, hacks, and flaky behaviors
- Encourage separation of concerns (use another module to create a security group)
- Requested and authored by @colinh6
- Stay current
references
- New API for EKS access control
- Obsoletes and closes #148
- Obsoletes and closes #155
- Obsoletes and closes #167
- Obsoletes and closes #168
- Obsoletes and closes #193
- Obsoletes and closes #202
- Fixes #203
- Supersedes and closes #173
- Supersedes and closes #194
- Supersedes and closes #195
- Supersedes and closes #196
- Supersedes and closes #197
- Supersedes and closes #198
- Supersedes and closes #199
- Supersedes and closes #200
- Supersedes and closes #201