feat: Add support for addon configuration_values
#2345
Conversation
| vpc-cni = {} | ||
| coredns = { | ||
| configuration_values = jsonencode({ | ||
| computeType = "Fargate" |
There was a problem hiding this comment.
Hi ! Sorry to ask here, but why is this needed ?
(and I agree its awesome)
There was a problem hiding this comment.
@auyer until now it was super hard to run this managed addon on fargate since it would default to ec2 and offered no option to change that.
One would have to run complex script to modify the deployment and that would complicate upgrades.
## [19.1.0](v19.0.4...v19.1.0) (2022-12-16) ### Features * Add support for addon `configuration_values` ([#2345](#2345)) ([3b62f6c](3b62f6c))
|
This PR is included in version 19.1.0 🎉 |
…ules#2345) Resolves undefined
## [19.1.0](terraform-aws-modules/terraform-aws-eks@v19.0.4...v19.1.0) (2022-12-16) ### Features * Add support for addon `configuration_values` ([terraform-aws-modules#2345](terraform-aws-modules#2345)) ([3b62f6c](terraform-aws-modules@3b62f6c))
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
configuration_valuesMotivation and Context
Breaking Changes
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request