v4.11.0

feat: support preserve and namespace_config on EKS add-ons John C. Bland II (@johncblandii) (#262)

## what

• Expose the preserve argument on the addons variable, plumbed through to the aws_eks_addon resource.
• Expose the add-on namespace (via the resource's namespace_config block) on the addons variable.
• Both fields are optional and default to null, so behavior is unchanged for existing callers.

why

• When an add-on is removed from Terraform management (for example when handing CoreDNS, the VPC CNI, or kube-proxy off to EKS Auto Mode), the module previously destroyed it with preserve defaulting to false, tearing down the underlying DaemonSet/Deployment. Setting preserve = true leaves the running Kubernetes resources in place so the hand-off is non-disruptive.
• namespace_config lets add-ons that support a configurable namespace install their resources into a custom namespace, which the module had no way to set.
• These were the only remaining configurable arguments of aws_eks_addon not surfaced by the module (the per-resource region override is intentionally left out to avoid drift on a regional cluster).

references

• aws_eks_addon resource