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:
@@ -51,7 +51,7 @@ graph LR;
|
||||
An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name-based virtual hosting. An [Ingress controller](/docs/concepts/services-networking/ingress-controllers) is responsible for fulfilling the Ingress, usually with a load balancer, though it may also configure your edge router or additional frontends to help handle the traffic.
|
||||
|
||||
An Ingress does not expose arbitrary ports or protocols. Exposing services other than HTTP and HTTPS to the internet typically
|
||||
uses a service of type [Service.Type=NodePort](/docs/concepts/services-networking/service/#nodeport) or
|
||||
uses a service of type [Service.Type=NodePort](/docs/concepts/services-networking/service/#type-nodeport) or
|
||||
[Service.Type=LoadBalancer](/docs/concepts/services-networking/service/#loadbalancer).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Reference in New Issue
Block a user