Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

I would like to be able to enable and disable creation of Helm charts individually instead of just relying on the global create_kubernetes_resources argument.

Describe the solution you would like

I would like to pass through an optional create_release variable on a per-addon basis, same as the underlying addons module.

Describe alternatives you have considered

As an alternative, we can use other Terraform resources or modules to create other resources independently of what gets installed to Kubernetes, but in some cases it is redundant (for example, Velero creates its own policies.) This also introduces the possibility of skew between our handcrafted configuration and what the module might provide.

Additional context

I, as an infrastructure operator, grant AWS account owners permission to define certain RBAC resources, as well as install Helm charts and other resources on their EKS clusters. They frequently adopt certain applications faster than me and my teammates. I would like to be able to help migrate them to Terraform-managed addons as the infra team makes them available. Using a "create resources only" workflow allows me to create an addon-managed configuration that I can test with the possibility of rolling back the existing Helm chart if necessary, only handing management over to Terraform if the new configuration is confirmed to work.

I have a fork of this repo to try to address this issue WIP.