New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting CNI daemonset environment variables like `WARM_IP_TARGET or HTT_PROXY` by reading a config file from the host ? #216

Open
nithu0115 opened this Issue Oct 31, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@nithu0115
Copy link

nithu0115 commented Oct 31, 2018

Is it possible to create a config file on the host like /etc/eks/xxx.config and dynamically populate those environment variable when CNI pod is starting ?

By default, we eks cni daemon set is started in kube-system namespaces. When launching the worker nodes behind proxy or if are using multiple subnets or HTTP_PROXY variables, we will have to go through the hassle of running kubectl edit/patch ds/aws-node -n kube-system and set those environment variables manually which requires user/role to have system:masters permission.

One more advantage of having config file on the host is, if I have multiple autoscaling groups with multiple instance types and if I have to set WARN_ENI_TARGET or WARM_IP_TARGET variables different, I can easily manage those from reading from the config file instead of centralized environment variable on the daemonset manifest yaml.

@craftyc0der

This comment has been minimized.

Copy link

craftyc0der commented Dec 17, 2018

I'd like to see WARM_IP_TARGET set as a tag in the ASG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment