aws
[service] [request]: Provide option to add http_proxy and no_proxy settings to VPC-CNI Addon in EKS
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request We want to have the possibility to configure http_proxy and no_proxy values as env variables for the vpc cni managed addon. Currently, we are using unmanaged addon and adding the following: (as mentioned here https://repost.aws/knowledge-center/eks-http-proxy-configuration-automation)
envFrom: - configMapRef: name: configmap-proxy-env
EKS now recommends migrating to managed addons so we would like to migrate frrom our custom unmanaged DS.
Which service(s) is this request for? EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
Our company has a strict network connectivity pattern where we need to expose proxy env variables to the aws-node DS.
Are you currently working around this issue?
We are using unmanaged vpc cni addon and specifying the proxy env.
Additional context Anything else we should know?
I can see that there was a similar request for the ebs csi driver that was implemented https://github.com/aws/containers-roadmap/issues/1850
Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Could this be widened to add a standard config option on all managed add-ons e.g Kube Proxy, ADOT etc..?
We still use the managed add-ons and deploy through Terraform but immediately after use a null_resource which triggers a script to run a kubectl set env to set the HTTP proxy env vars.
