I'm diving into Cilium and I've learned that EKS Anywhere supports it by default, but I'm trying to figure out how to replace the default VPC CNI (ENI) and kube-proxy with Cilium ENI on regular EKS. Has anyone tackled this? Any tips or experiences would be greatly appreciated!
1 Answer
Yeah, it works perfectly! We actually have it running in production. The Cilium documentation includes some specific guidelines for deploying it on EKS, so that's definitely your go-to resource.
I’m setting it up using Terraform/OpenTofu. Even when I enable ENI and set kubeproxyreplacement to true, I lose the EKS API connection once I remove aws-node and kube-proxy. Did you set it up with Terraform?