1 Answer
- Newest
- Most votes
- Most comments
2
Hi,
If you read the release note correctly, it does mention:
When changes are made to underlying VPC resources, such as new subnets associated with VPC expansion, existing EKS clusters can now be updated to stay in sync without the need to create new clusters.
Moreover, if you look at the original GitHub Issue [1], there's a note which says:
The subnets passed through an update API call must comprise the same set of AZs as originally passed when creating the cluster.
These points make it clear enough that it is possible to add more subnets.
References:
[1] https://github.com/aws/containers-roadmap/issues/170#issuecomment-1777947349
Thanks,
Atul
answered 7 months ago
Relevant content
- asked a year ago
- Accepted Answerasked 10 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Thank you! I just want to double confirm.