Skip to content

Commit ea3b034

Browse files
committed
restored h2
1 parent 62b1a71 commit ea3b034

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/aks/concepts-network.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ In a container-based, microservices approach to application development, applica
1818

1919
This article introduces the core concepts that provide networking to your applications in AKS:
2020

21-
* [Services and ServiceTypes](#services-and-servicetypes)
21+
* [Services and ServiceTypes](#services)
2222
* [Azure virtual networks](#azure-virtual-networks)
2323
* [Ingress controllers](#ingress-controllers)
2424
* [Network policies](#network-policies)
@@ -38,7 +38,7 @@ In Kubernetes:
3838

3939
The Azure platform also simplifies virtual networking for AKS clusters. When you create a Kubernetes load balancer, you also create and configure the underlying Azure load balancer resource. 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.
4040

41-
## Services and ServiceTypes
41+
## Services
4242

4343
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].
4444

0 commit comments

Comments
 (0)