Skip to content

Commit 07d143e

Browse files
author
craigcaseyMSFT
committed
fixing broken llink issue
1 parent 7e3a71d commit 07d143e

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/aks/concepts-network.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,6 @@ In a container-based microservices approach to application development, applicat
1616

1717
This article introduces the core concepts that provide networking to your applications in AKS:
1818

19-
- [Services](#services)
2019
- [Azure virtual networks](#azure-virtual-networks)
2120
- [Ingress controllers](#ingress-controllers)
2221
- [Network policies](#network-policies)
@@ -29,8 +28,6 @@ In Kubernetes, *Services* logically group pods to allow for direct access via an
2928

3029
The Azure platform also helps to simplify virtual networking for AKS clusters. When you create a Kubernetes load balancer, the underlying Azure load balancer resource is created and configured. As you open network ports to pods, the corresponding Azure network security group rules are configured. For HTTP application routing, Azure can also configure *external DNS* as new ingress routes are configured.
3130

32-
## Services
33-
3431
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:
3532

3633
- **Cluster IP** - Creates an internal IP address for use within the AKS cluster. Good for internal-only applications that support other workloads within the cluster.

0 commit comments

Comments
 (0)