Open sprilutsky01 opened 2 years ago
@phealy can you take a look at this?
Any update on the below?
Regards, Sergey Prilutsky
From: Amanda Wang @.> Sent: Friday, September 16, 2022 4:11 PM To: Azure/AKS @.> Cc: sprilutsky01 @.>; Author @.> Subject: Re: [Azure/AKS] HTTP_PROXY configuration (Issue #3195)
@phealyhttps://github.com/phealy can you take a look at this?
— Reply to this email directly, view it on GitHubhttps://github.com/Azure/AKS/issues/3195#issuecomment-1249820934, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AG2V6CIZLDBCGF5H66UWTZTV6TPAJANCNFSM6AAAAAAQKWMOGM. You are receiving this because you authored the thread.Message ID: @.***>
Any update on the below?
Regards, Sergey Prilutsky
From: Amanda Wang @.> Sent: Friday, September 16, 2022 4:11 PM To: Azure/AKS @.> Cc: sprilutsky01 @.>; Author @.> Subject: Re: [Azure/AKS] HTTP_PROXY configuration (Issue #3195)
@phealyhttps://github.com/phealy can you take a look at this?
— Reply to this email directly, view it on GitHubhttps://github.com/Azure/AKS/issues/3195#issuecomment-1249820934, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AG2V6CIZLDBCGF5H66UWTZTV6TPAJANCNFSM6AAAAAAQKWMOGM. You are receiving this because you authored the thread.Message ID: @.***>
Action required from @Azure/aks-pm
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Hi AKS team(s),
The issue has been opened on 9/16/2022. Please take a look and hopefully Microsoft can take an action soon.
Regards, Sergey Prilutsky
From: microsoft-github-policy-service[bot] @.> Sent: Sunday, February 18, 2024 1:20 PM To: Azure/AKS @.> Cc: sprilutsky01 @.>; Author @.> Subject: Re: [Azure/AKS] HTTP_PROXY configuration (Issue #3195)
Issue needing attention of @Azure/aks-leadshttps://github.com/orgs/Azure/teams/aks-leads
— Reply to this email directly, view it on GitHubhttps://github.com/Azure/AKS/issues/3195#issuecomment-1951419966, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AG2V6CPQUJGMBVEX6ZKAG3LYUJH6DAVCNFSM6AAAAAAQKWMOGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRGQYTSOJWGY. You are receiving this because you authored the thread.Message ID: @.***>
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Is your feature request related to a problem? Please describe. The way AKS HTTP_PROXY configuration works, it always try to go to the specified Proxy (unless you can specify it on NO_PROXY for specific app or 3rd party infrastructure feature (LinkerD, Grafana, Prometheus, Aqua Sec, etc).
Describe the solution you'd like HTTP_PROXY config feature should be smart enough to figure out when it is actually required to go beyond vNET/Subnet through the Proxy out to the internet. Communication between pods, should not involve HTTP_PROXY/NO_PROXY.
It should be designed and engineered the3 same way vNET/VLAN routing works: if the network traffic flies through the same vNET/VLAN, no need to have a route and go outside
Describe alternatives you've considered In some cases NO_PROXY works, in the other requires to rebuild AKS cluster. Cluster rebuild is not acceptable by many customers and I totally agree withy that.
Additional context