Hello everyone, I'm encountering the following issue: I have an AKS cluster deployed inside my own VNET using Azure CNI with Cilium, default settings The AKS cluster has application routing module installed on it. I have two Load Balancers created with the use of NginxIngressController: External + Internal I have a K8s service exposed through the internal LB with the use of an ingress I can access the service through the LB ip from within the VNET and from within my own on-premise network connected to the Azure VNET through VPN (gateways setup). I've recently peered another Azure VNET (in another subscription) to mine. The devices in the peered Azure VNET can't connect to the service through the LB ip (getting timeouts). The devices in the peered Azure VNET can ping and connect to the AKS nodes in my own VNET directly. Can someone please help point me in the right direction? What am I doing wrong? Thank you, Bogdan

AKS - Application routing

Bogdan Melinte 0

Hello everyone,

I'm encountering the following issue:

I have an AKS cluster deployed inside my own VNET using Azure CNI with Cilium, default settings
The AKS cluster has application routing module installed on it.
I have two Load Balancers created with the use of NginxIngressController: External + Internal
I have a K8s service exposed through the internal LB with the use of an ingress
I can access the service through the LB ip from within the VNET and from within my own on-premise network connected to the Azure VNET through VPN (gateways setup).
I've recently peered another Azure VNET (in another subscription) to mine.
The devices in the peered Azure VNET can't connect to the service through the LB ip (getting timeouts).
The devices in the peered Azure VNET can ping and connect to the AKS nodes in my own VNET directly.

Can someone please help point me in the right direction? What am I doing wrong?

Thank you,

Bogdan

0 comments