Roee Landesman

Wanted to follow up on this and say that this did work for me, might be a stale issue

`v1.16.2-eksbuild.1` on EKS 1.25 Config (used for DD scrape of prometheus-compatible metrics endpoint): ``` resource "aws_eks_addon" "vpc_cni_addon" { cluster_name = module.eks.cluster_id addon_name = "vpc-cni" addon_version = data.aws_eks_addon_version.vpc_cni_latest.version resolve_conflicts = "OVERWRITE"...

My bad, copied the wrong config. Same concept applies to the `kube-proxy` addon

Great resource, thank you @nitrocode for putting this together. One caveat, the service template today doesn't allow for port names and will error on usage of a string (i.e `use-annotations`)....

Not a great workaround but I basically took your code and converted it into a `kubernetes_ingress_v1 ` TF object: ```hcl resource "kubernetes_ingress_v1" "webhook_ingress" { metadata { name = "atlantis-webhook" namespace...

@mengdic is there an ETA for `10.x` ?