Issue with Deployment of Mendix app on Azure Kubernetes Service

0
I've deployed a Mendix app on a Kubernetes Cluster using Azure Kubernetes Service (AKS). When the build is ready, it generates the App URL, however, it appears to be generated with IP numbers and I can't establish a connection correctly.
asked
1 answers
0

What you are seeing is usually related to DNS and Ingress configuration, not the Mendix app itself.


When deploying Mendix on AKS, the URL shown in the Mendix Portal often points to the public IP of the Load Balancer. However, the Ingress controller (commonly NGINX) typically expects a hostname, not a raw IP address, to correctly route traffic to the Mendix application.


If you try to access the app directly via the IP address, the Ingress controller may not find a matching host rule and the request can fail or return a timeout.


A common fix is to map a DNS name to the public IP of the Load Balancer. In Azure, you can go to Public IP addresses, locate the IP created for your AKS cluster, and assign a DNS name label (for example myapp.eastus.cloudapp.azure.com). After that, use this hostname as the App URL instead of the raw IP.


It is also worth checking whether the IP is public or private. If it is a private IP (for example starting with 10.x, 172.x, or 192.168.x), the app will only be reachable from within the network or through VPN.


Additionally, verify that the Ingress controller is running correctly and that the NSG/firewall rules allow inbound traffic on ports 80 and 443.


So the main things to check are:

DNS mapping for the Load Balancer IP,

Ingress configuration,

whether the IP is public or private,

and the network security rules.


If this resolves your issue, please mark it as accepted.


answered