Skip to content

Commit 128f1de

Browse files
chasewilsonchasewilson
committed
[AKS] - Split AKS Ingress Conceptual doc
1 parent bfa98cd commit 128f1de

File tree

3 files changed

+78
-3
lines changed

3 files changed

+78
-3
lines changed

‎articles/aks/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -148,6 +148,8 @@
148148
href: concepts-network-ip-address-planning.md
149149
- name: Services
150150
href: concepts-network-services.md
151+
- name: Ingress
152+
href: concepts-network-ingress.md
151153
- name: Advanced Container Networking Services
152154
items:
153155
- name: Advanced Container Networking Services overview

‎articles/aks/concepts-network-ingress.md

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
---
2+
title: Concepts - Ingress Networking in Azure Kubernetes Service (AKS)
3+
description: Learn about ingress networking in Azure Kubernetes Service (AKS) including ingress controllers
4+
ms.topic: conceptual
5+
ms.date: 06/03/2024
6+
author: schaffererin
7+
ms.author: schaffererin
8+
---
9+
# Ingress in Azure Kubernetes Service (AKS)
10+
11+
Ingress in AKS is a Kubernetes resource that manages external HTTP-like traffic access to [services][services] within a cluster. An AKS ingress may provide services like load balancing, SSL termination, and name-based virtual hosting. For more information about Kubernetes Ingress, see the [Kubernetes Ingress documentation][k8s-ingress].
12+
13+
## Ingress controllers
14+
15+
When managing application traffic, Ingress controllers provide advanced capabilities by operating at layer 7. They can route HTTP traffic to different applications based on the inbound URL, allowing for more intelligent and flexible traffic distribution rules. For example, an ingress controller can direct traffic to different microservices depending on the URL path, enhancing the efficiency and organization of your services.
16+
17+
On the other hand, a LoadBalancer-type Service, when created, sets up an underlying Azure load balancer resource. This load balancer works at layer 4, distributing traffic to the pods in your Service on a specified port. However, layer 4 services are unaware of the actual applications and can't implement these types of complex routing rules.
18+
19+
Understanding the distinction between these two approaches helps in selecting the right tool for your traffic management needs.
20+
21+
![Diagram showing Ingress traffic flow in an AKS cluster][aks-ingress]
22+
23+
### Compare ingress options
24+
25+
The following table lists the feature differences between the different ingress controller options:
26+
27+
| Feature | Application Routing addon | Application Gateway for Containers | Azure Service Mesh/Istio-based service mesh |
28+
|---------------------------------------------------|---------------------------|------------------------------------------|---------------------------------------------|
29+
| **Ingress/Gateway controller** | NGINX ingress controller | Azure Application Gateway for Containers | Istio Ingress Gateway |
30+
| **API** | Ingress API | Ingress API and Gateway API | Gateway API |
31+
| **Hosting** | In-cluster | Azure hosted | In-cluster |
32+
| **Scaling** | Autoscaling | Autoscaling | Autoscaling |
33+
| **Load balancing** | Internal/External | External | Internal/External |
34+
| **SSL termination** | In-cluster | Yes: Offloading and E2E SSL | In-cluster |
35+
| **mTLS** | N/A | Yes to backend | N/A |
36+
| **Static IP Address** | N/A | FQDN | N/A |
37+
| **Azure Key Vault stored SSL certificates** | Yes | Yes | N/A |
38+
| **Azure DNS integration for DNS zone management** | Yes | Yes | N/A |
39+
40+
The following table lists the different scenarios where you might use each ingress controller:
41+
42+
| Ingress option | When to use |
43+
|----------------|-------------|
44+
| **Managed NGINX - Application Routing addon** | • In-cluster hosted, customizable, and scalable NGINX ingress controllers. </br> • Basic load balancing and routing capabilities. </br> • Internal and external load balancer configuration. </br> • Static IP address configuration. </br> • Integration with Azure Key Vault for certificate management. </br> • Integration with Azure DNS Zones for public and private DNS management. </br> • Supports the Ingress API. |
45+
| **Application Gateway for Containers** | • Azure hosted ingress gateway. </br> • Flexible deployment strategies managed by the controller or bring your own Application Gateway for Containers. </br> • Advanced traffic management features such as automatic retries, availability zone resiliency, mutual authentication (mTLS) to backend target, traffic splitting / weighted round robin, and autoscaling. </br> • Integration with Azure Key Vault for certificate management. </br> • Integration with Azure DNS Zones for public and private DNS management. </br> • Supports the Ingress and Gateway APIs. |
46+
| **Istio Ingress Gateway** | • Based on Envoy, when using with Istio for a service mesh. </br> • Advanced traffic management features such as rate limiting and circuit breaking. </br> • Support for mTLS </br> • Supports the Gateway API. |
47+
48+
### Create an Ingress resource
49+
50+
The application routing addon is the recommended way to configure an Ingress controller in AKS. The application routing addon is a fully managed ingress controller for Azure Kubernetes Service (AKS) that provides the following features:
51+
52+
- Easy configuration of managed NGINX Ingress controllers based on Kubernetes NGINX Ingress controller.
53+
54+
- Integration with Azure DNS for public and private zone management.
55+
56+
- SSL termination with certificates stored in Azure Key Vault.
57+
58+
For more information about the application routing addon, see [Managed NGINX ingress with the application routing add-on](app-routing.md).
59+
60+
### Client source IP preservation
61+
62+
Configure your ingress controller to preserve the client source IP on requests to containers in your AKS cluster. When your ingress controller routes a client's request to a container in your AKS cluster, the original source IP of that request is unavailable to the target container. When you enable *client source IP preservation*, the source IP for the client is available in the request header under *X-Forwarded-For*.
63+
64+
If you're using client source IP preservation on your ingress controller, you can't use TLS pass-through. Client source IP preservation and TLS pass-through can be used with other services, such as the *LoadBalancer* type.
65+
66+
To learn more about client source IP preservation, see [How client source IP preservation works for LoadBalancer Services in AKS][ip-preservation].
67+
68+
<!-- IMAGES -->
69+
[aks-ingress]: ./media/concepts-network/aks-ingress.png
70+
71+
<!-- LINKS - External -->
72+
[k8s-ingress]: https://kubernetes.io/docs/concepts/services-networking/ingress/
73+
74+
<!-- LINKS - Internal -->
75+
[ip-preservation]: https://techcommunity.microsoft.com/t5/fasttrack-for-azure/how-client-source-ip-preservation-works-for-loadbalancer/ba-p/3033722#:~:text=Enable%20Client%20source%20IP%20preservation%201%20Edit%20loadbalancer,is%20the%20same%20as%20the%20source%20IP%20%28srjumpbox%29.
76+
[services]: concepts-network-services.md

‎articles/aks/concepts-network.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,6 @@ In AKS, you can deploy a cluster that uses one of the following network models:
5252
* **Overlay network model**: Overlay networking is the most common networking model used in Kubernetes. Pods are given an IP address from a private, logically separate CIDR from the Azure virtual network subnet where AKS nodes are deployed. This model enables simpler, improved scalability when compared to the flat network model.
5353
* **Flat network model**: A flat network model in AKS assigns IP addresses to pods from a subnet from the same Azure virtual network as the AKS nodes. Any traffic leaving your clusters isn't SNAT'd, and the pod IP address is directly exposed to the destination. This model can be useful for scenarios like exposing pod IP addresses to external services.
5454

55-
56-
57-
5855
For more information on networking models in AKS, see [CNI Networking in AKS][network-cni-overview].
5956

6057
## Ingress controllers

0 commit comments

Comments
 (0)