You can set these environment variables as part of your Terraform Configuration. To have flexibility in configuring the env of the CNI, you can set the env outside of your Terraform Configuration as well.
You can also write a script that will generate all the env you want to set using the
kubectl command. Use Terraform to launch the script.
WARM_IP_TARGET to 5 for example, you can use the command below:
kubectl set env ds aws-node -n kube-system WARM_IP_TARGET=5
See more info on the CNI ENVs
EKS Fargate: restrict access to service to only certain podsasked 6 months ago
[EKS] Use Multus with existing cluster created by eksctlasked 6 months ago
OKTA EKS Atlassian suite integrationasked 2 months ago
EKS: ARM64 nodes fail to become ready due to CNI errorasked 9 months ago
EKS VPC-CNI Plugin Node Group Setup Questionsasked 4 months ago
Adding our own worker to MWAAasked 2 years ago
How to pass environment variables to CNI Addon?asked a month ago
EKS Upgrade Failed from 1.13 to 1.14asked 2 years ago
Trying to use environment variablesasked 2 years ago
Update EKS 1.16 managed worker nodes with 1.16 AMI do not join the clusterasked 2 years ago