Fix broken anchor link of #type-nodeport in service.md (#30388)

* Fix broken anchor link of #type-nodeport in service.md

* Update anchor link from #nodeport to #type-nodeport

Update anchor link from #nodeport to #type-nodeport in overview.md

* Update anchor link from #nodeport to #type-nodeport

Update anchor link from #nodeport to #type-nodeport in ingress.md

* Update anchor link from #nodeport to #type-nodeport

Update anchor link from #nodeport to #type-nodeport in troubleshooting-kubeadm.md

* Update anchor link from #nodeport to #type-nodeport

Update anchor link from #nodeport to #type-nodeport in connecting-frontend-backend.md

* Update anchor link from #nodeport to #type-nodeport

Update anchor link from #nodeport to #type-nodeport in source-ip.md
This commit is contained in:
sandipanpanda
2021-11-12 21:32:28 +05:30
committed by GitHub
parent 152082f1db
commit 7a513e6dee
6 changed files with 6 additions and 6 deletions
@@ -159,7 +159,7 @@ Calico, Canal, and Flannel CNI providers are verified to support HostPort.
For more information, see the [CNI portmap documentation](https://github.com/containernetworking/plugins/blob/master/plugins/meta/portmap/README.md).
If your network provider does not support the portmap CNI plugin, you may need to use the [NodePort feature of
services](/docs/concepts/services-networking/service/#nodeport) or use `HostNetwork=true`.
services](/docs/concepts/services-networking/service/#type-nodeport) or use `HostNetwork=true`.
## Pods are not accessible via their Service IP