Azure kubernetes with internal and external load balancer

Question

We have AKS Setup which handles public web site requests which is taken care by kubernetes public load balancer and outbound traffic.
We now have requirement to add internal load balancer which needs to use vnet address space privaete IP and communicate to on prem services. Site to Site VPN connection is established and it is working fine.
My question is :

1. Can we create another internal load balancer and add kubernetes vmss as back end pool
2. How to take care of private and public traffic

Answer 1

@Sankararaman, Sivakumar Apologies for the delay in response and all the inconvenience caused because of the issue.

This can be found on our docs:

Create an internal load balancer - Azure Kubernetes Service | Microsoft Learn

If you are using an ingress controller for these load balancers you might want to look at both ingress.class spec, which has had a deprecated annotation in Kubernetes below 1.18.

Ingress | Kubernetes

Deprecation:
Ingress | Kubernetes

FYI, two ingress controllers can be deployed, one public and one private and using two different ingress classes can then serve either public or private traffic.

If you are just mapping a Service that talks to a particular Pod as a LoadBalancer, you can stick to the first link.

You could also use an App Gateway with a private IP address and AGIC.

Here are docs on the topic: https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-overview

Hope it helps!!!

Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.