Closed zycon closed 3 years ago
Hi zycon, AKS bot here :wave: Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.
I might be just a bot, but I'm told my suggestions are normally quite good, as such: 1) If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster. 2) Please abide by the AKS repo Guidelines and Code of Conduct. 3) If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics? 4) Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS. 5) Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue. 6) If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
Triage required from @Azure/aks-pm
Action required from @Azure/aks-pm
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
For Private outbound use a Private Cluster
Triage required from @Azure/aks-pm
Thanks for reaching out. I'm closing this issue as it was marked with "Answer Provided" and it hasn't had activity for 2 days.
No possible way to create a private outbound load balancer for egress traffic. Inbound address of pod's needs to be whitelisted in client firewall, but couldn't find any feasible way unless mentioning the aks cidr range
Either a internal NAT gateway for egress traffic or internal loadbalancer which supports egress traffic
AKS private cluster, and having custom checkpoint firewall which facilitates the site-to-site vpn