EKS teams struggle to make cluster changes safely with Terraform
EKS operators face failure-prone cluster changes: upgrades must happen sequentially, and add-on compatibility problems can trigger cascading remediation. Terraform users also report difficulty patching existing Kubernetes resources declaratively, while undersized subnet CIDRs can leave too few IPs for pods. The reports point to piecemeal workarounds rather than a dependable workflow for checking and applying EKS changes.
For platform and infrastructure teams running Amazon EKS with Terraform. Mentioned from May 2020 to Apr 2024 on GitHub and Hacker News.
5 different people described this problem in 3 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 6.8/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
Often, it's far more efficient to build an entirely new cluster from scratch and then cut over - which seems ridiculous
For now we can't patch existing EKS CoreDNS with terraform so we have to install 3rd party CoreDNS helm chart at the beginning
eugene-burachevskiy on GitHub (hashicorp/terraform-provider-kubernetes)May 2020Asked for a toolHas a workaround
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks