[Request]: Provide option to add http_proxy and no_proxy settings to AWS-EFS-CSI-Driver Addon in EKS
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
**Tell us about your request**
Give the user an option to configure http_proxy and no_proxy values when installed aws-efs-csi-0driver using EKS Addon functionality.
**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?**
Projects which have strict network connectivity like those of the public domains need a mechanism to expose proxy values to connect to the internet in a secure way.
**Are you currently working around this issue?**
We are mitigating this issue by installing the driver using helm chart which adding more code
**Additional context**
Error Message when no proxy config is provided
I0415 13:26:01.859838 1 controller.go:84] CreateVolume: called with args {Name:pvc-18959573-e1aa-485c-8fbd-68ed1116755f CapacityRange:required_bytes:21474836480 VolumeCapabilities:[mount: access_mode: ] Parameters:map[csi.storage.k8s.io/pv/name:pvc-18959573-e1aa-485c-8fbd-68ed1116755f csi.storage.k8s.io/pvc/name:efs-claim csi.storage.k8s.io/pvc/namespace:default directoryPerms:700 ensureUniqueDirectory:false fileSystemId:fs-02b1601365b880891 gidRangeEnd:2000 gidRangeStart:1000 provisioningMode:efs-ap subPathPattern:/${.PVC.name}] Secrets:map[] VolumeContentSource: AccessibilityRequirements: XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}
E0415 13:26:11.860349 1 driver.go:111] GRPC error: rpc error: code = Internal desc = Failed to fetch Access Points or Describe File System: List Access Points failed: operation error EFS: DescribeAccessPoints, https response error StatusCode: 0, RequestID: , canceled, context deadline exceeded
Contributor guide
Research direction
Start by reviewing the AWS EFS CSI Driver's EKS Addon functionality and compare it with the Helm chart workaround described in the issue. Confirm how http_proxy and no_proxy are configured and exposed, then verify that an EKS Addon installation can provide those values and connect successfully through the proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100