(eks-mcp-server): Add support for NO_PROXY #2438
Description
Describe the feature
The _configure_proxy_settings method in k8s_apis.py sets configuration.proxy when HTTP_PROXY/HTTPS_PROXY are present, but does not check for NO_PROXY/no_proxy before doing so.
Use Case
This breaks environments where the proxy is set globally, but EKS API endpoints should be accessed directly via Direct Connect.
Proposed Solution
If the K8s API server's domain name part matches a NO_PROXY entry, proxy should not be configured on the Kubernetes client.
urllib.request.proxy_bypass_environment() might be used to check the target hostname against NO_PROXY before setting configuration.proxy.
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change