Edit

Plan application networking for Azure Kubernetes Service (AKS)

In this article, you learn application networking options for Azure Kubernetes Service (AKS). We first pose a question to help guide your planning, and then provide options, recommendations, and best practices.

How do you want to access your applications?

Application networking controls how clients access applications running in your Kubernetes pods and how services communicate within and across clusters.

Application networking options

Choose application networking options based on whether you need to expose applications to clients outside the cluster or manage service-to-service communication:

Application networking option Features & functionality
Load Balancer Service • Uses a Kubernetes LoadBalancer Service to directly expose an application on a public or private IP.
• Supports multiple ports and any TCP or UDP traffic.
• Requires at least one unique IP:port pair per application.
Ingress controllers • Exposes an application behind a layer-7 reverse proxy.
• Usable only for HTTP-like traffic (HTTP, HTTPS, gRPC).
• Can share a single public IP and ports for all ingress definitions on the same ingress controller.
• Managed ingress options include: Managed ingress-nginx through the application routing add-on, Azure Application Gateway for Containers (recommended), and Istio ingress gateway.
Azure Kubernetes Application Network (preview) • Provides managed, sidecar-free service-to-service communication within and across AKS member clusters.
• Provides mTLS and workload identity for enrolled services, with optional layer-7 routing and authorization.
• Manages the service-network control plane and data plane.
• Doesn't replace application ingress or create underlying cross-cluster network connectivity.

Recommendations

For clients accessing applications from outside the cluster, use Load Balancer Service with layer-4 load balancing for non-HTTP traffic. This approach provides direct access to your applications and supports a wide range of protocols. For HTTP-like traffic, use Ingress controllers with layer-7 load balancing. This approach allows you to take advantage of advanced routing features and share a single public IP for multiple applications.

For service-to-service communication, consider Azure Kubernetes Application Network (preview) when you need managed workload identity, mTLS, and traffic policies without sidecars. Review its preview status and current limitations before adoption, and plan ingress and underlying network connectivity separately.