Fix broken links. (#9755)

- /docs/concepts/services-networking/service/#type-nodeport => /docs/concepts/services-networking/service/#nodeport
- /docs/concepts/services-networking/service/#type-loadbalancer => /docs/concepts/services-networking/service/#loadbalancer
- https://github.com/kubernetes/ingress-nginx/blob/master/docs/ingress-controller-catalog.md => https://github.com/kubernetes/ingress-nginx/
This commit is contained in:
Slava Semushin
2018-08-17 18:00:10 +01:00
committed by k8s-ci-robot
parent 8c02f4caa4
commit 5f19d7ced8
12 changed files with 18 additions and 18 deletions
@@ -52,7 +52,7 @@ This is a living document. If you think of something that is not on this list bu
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/#type-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/#nodeport) Service before resorting to `hostPort`.
- Avoid using `hostNetwork`, for the same reasons as `hostPort`.