feat: allow disabling default EKS addons via cluster_addons_disable
Currently (starting from version 1.2.2), the module merges local.cluster_addons
(default addons) with var.cluster_addons
(user-provided), using:
cluster_addons = merge(local.cluster_addons, var.cluster_addons)
This means Users can override default addon configuration, but cannot remove a default addon
- Some use cases (e.g., orchestrating VPC CNI, node group, then coredns) require not creating certain addons by default - eg: this is required for custom CNI configuration for Mulesoft cluster.
Proposed Solution
Introduce a new variable: cluster_addons_disable
with List of addon names to exclude from creation, even if present in defaults.
Migration/Compatibility
-
Backward compatible: If
cluster_addons_disable
is not set, behavior is unchanged. so there is no breaking changes