whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
* 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
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/configuration/overview.md
+1 -1
View File
@@ -55,7 +55,7 @@ DNS server watches the Kubernetes API for new `Services` and creates a set of DN
If you only need access to the port for debugging purposes, you can use the [apiserver proxy](/docs/tasks/access-application-cluster/access-cluster/#manually-constructing-apiserver-proxy-urls) or [`kubectl port-forward`](/docs/tasks/access-application-cluster/port-forward-access-application-cluster/).
If you explicitly need to expose a Pod's port on the node, consider using a [NodePort](/docs/concepts/services-networking/service/#nodeport) Service before resorting to `hostPort`.
If you explicitly need to expose a Pod's port on the node, consider using a [NodePort](/docs/concepts/services-networking/service/#type-nodeport) Service before resorting to `hostPort`.
- Avoid using `hostNetwork`, for the same reasons as `hostPort`.