You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/concepts-network.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Concepts - Networking in Azure Kubernetes Services (AKS)
3
3
description: Learn about networking in Azure Kubernetes Service (AKS), including kubenet and Azure CNI networking, ingress controllers, load balancers, and static IP addresses.
4
4
ms.topic: conceptual
5
-
ms.date: 11/18/2022
5
+
ms.date: 12/01/2022
6
6
ms.custom: fasttrack-edit
7
7
8
8
---
@@ -18,7 +18,7 @@ In a container-based, microservices approach to application development, applica
18
18
19
19
This article introduces the core concepts that provide networking to your applications in AKS:
@@ -30,6 +30,7 @@ To allow access to your applications or between application components, Kubernet
30
30
In Kubernetes:
31
31
32
32
**Services* logically group pods to allow for direct access on a specific port via an IP address or DNS name.
33
+
**ServiceTypes* allow you to specify what kind of Service you want.
33
34
* You can distribute traffic using a *load balancer*.
34
35
* More complex routing of application traffic can also be achieved with *ingress controllers*.
35
36
* You can *control outbound (egress) traffic* for cluster nodes.
@@ -39,11 +40,13 @@ The Azure platform also simplifies virtual networking for AKS clusters. When you
39
40
40
41
## Services
41
42
42
-
To simplify the network configuration for application workloads, Kubernetes uses *Services* to logically group a set of pods together and provide network connectivity. The following Service types are available:
43
+
To simplify the network configuration for application workloads, Kubernetes uses *Services* to logically group a set of pods together and provide network connectivity. You can specify a Kubernetes *ServiceType* to specify what kind of Service you want, for example if you want to expose a Service onto an external IP address that's outside of your cluster. For more information, see the Kubernetes documentation for [Publishing Services (ServiceTypes)][service-types].
44
+
45
+
The following ServiceTypes are available:
43
46
44
47
***ClusterIP**
45
48
46
-
ClusterIP creates an internal IP address for use within the AKS cluster. This Service is good for *internal-only applications* that support other workloads within the cluster.
49
+
ClusterIP creates an internal IP address for use within the AKS cluster. This Service is good for *internal-only applications* that support other workloads within the cluster. This is the default that's used if you don't explicitly specify a type for a Service.
47
50
48
51
![Diagram showing ClusterIP traffic flow in an AKS cluster][aks-clusterip]
49
52
@@ -55,7 +58,7 @@ To simplify the network configuration for application workloads, Kubernetes uses
55
58
56
59
***LoadBalancer**
57
60
58
-
Creates an Azure load balancer resource, configures an external IP address, and connects the requested pods to the load balancer backend pool. To allow customers' traffic to reach the application, load balancing rules are created on the desired ports.
61
+
LoadBalancer creates an Azure load balancer resource, configures an external IP address, and connects the requested pods to the load balancer backend pool. To allow customers' traffic to reach the application, load balancing rules are created on the desired ports.
59
62
60
63
![Diagram showing Load Balancer traffic flow in an AKS cluster][aks-loadbalancer]
61
64
@@ -242,6 +245,7 @@ For more information on core Kubernetes and AKS concepts, see the following arti
0 commit comments