AGIC ingress on AKS unabled to populate status.loadbalancer.ingress when in two different resource group

Morten Lund Jakobsen 0 Reputation points
2025-02-11T13:49:57.0966667+00:00

Hello Microsoft.

I'm trying to create a structure within my organization where I use the same virtual network for all AKS clusters so that if need be they can communicate security and locally inside a Virtual Network within Azure.

My Issue:

Information:

Resource group = "rg"

VNet, X, in rg vnet_rg

AGIC, Y, in rg appgw_rg

AKS, Z, in rg cluster_rg

Node pool J in rg NodeResourceGroup

Load balancer with external IP, in NodeResourceGroup

My Kubernetes cluster is deployed through Argo CD with my application on a different cluster than where the actual Ingress resource is located (on a different cluster).

Based on my previous deployment, this works when the gateway, VNet, and load balancer are in the same VNet. However, I want to avoid using the same resource group for multiple different resources in Azure to create a better structure and overview.

When I then deploy an application with the necessary things I can get my application properly exposed to internet and actual connect to it, but when the ingress is deployed it's in a never ending progressing state because it can't get the loadbalancer IP.

What my question is, is there any where for me to tell the ingress deployment in k8s where to find or locate the loadbalancer? When it was all the same rg, the ingress deployment would populate these credentials it self, but now when it not populated, im unsure if there actually are loadbalancing for my k8s cluster apps through the gateway.

Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,462 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.