migrate the K8s networking model section

kubernetes · Jun 25, 2021 · c8cc8af · c8cc8af
1 parent 99913aa
commit c8cc8af
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 3 deletions.
diff --git a/content/en/docs/concepts/cluster-administration/networking.md b/content/en/docs/concepts/cluster-administration/networking.md
@@ -30,8 +30,7 @@ insert dynamic port numbers into configuration blocks, services have to know
 how to find each other, etc.  Rather than deal with this, Kubernetes takes a
 different approach.
 
-To learn about the Kubernetes networking model, see [here](/docs/concepts/services-networking/_index.md).
-
+To learn about the Kubernetes networking model, see [here](/docs/concepts/services-networking/).
 
 ## How to implement the Kubernetes networking model
 

diff --git a/content/en/docs/concepts/services-networking/_index.md b/content/en/docs/concepts/services-networking/_index.md
@@ -46,7 +46,6 @@ It is possible to request ports on the `Node` itself which forward to your `Pod`
 implemented is also a detail of the container runtime. The `Pod` itself is
 blind to the existence or non-existence of host ports.
 
-
 Kubernetes networking addresses four concerns:
 - Containers within a Pod use networking to communicate via loopback.
 - Cluster networking provides communication between different Pods.