Azure
Static egress for AKS Deployment
Public Preview ETA: 10/14/2024 *
- ETA is only an estimation, this date could change but will be updated if it does.
What happened:
I have a Public IP(for.eg PUB_IP_2) Based Load Balancer assigned to a service(for.eg SRV_1) in AKS.
Lets say that service SRV_1 is calling another Service(SRV_XYZ) which is outside AKS and gets some response back. The outside service (SRV_XYZ) allows calls only from IP Address(PUB_IP_2) but it actually receives call from the Public IP(for.e.g PUB_IP_1) of AKS Cluster
What you expected to happen: A mechanism to specify that any incoming call coming to PUB_IP_2 should be forwarded to the intended places(say outside AKS cluster places) by PUB_IP_2 only and not by AKS Public IP(PUB_IP_1)
How to reproduce it (as minimally and precisely as possible):
- Create Public IP Based AKS Cluster
- Create a Service inside it having Public IP Based Load Balancer
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version): 1.18 - Size of cluster (how many worker nodes are in the cluster?) 1
- General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.)
- Others:
Hi swapnilpotnis, 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:
- If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
- Please abide by the AKS repo Guidelines and Code of Conduct.
- If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
- Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
- 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.
- If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
The load balancer IP addresses that are part of the outbound pool are all used by the backend pool, this means any of them can be used, you can't control/specify a specific one per service. This is a feature request we're looking into, which allows you to specify specific egress IPs per service.
A way to do this soon is when we release multiple load balancer support #2174, you can add a specific LB (and respective outbound IP) per nodepool.
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.