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/services-networking/service.md
+1 -1
View File
@@ -568,7 +568,7 @@ The default is `ClusterIP`.
You can also use [Ingress](/docs/concepts/services-networking/ingress/) to expose your Service. Ingress is not a Service type, but it acts as the entry point for your cluster. It lets you consolidate your routing rules
into a single resource as it can expose multiple services under the same IP address.
### Type NodePort {#nodeport}
### Type NodePort {#type-nodeport}
If you set the `type` field to `NodePort`, the Kubernetes control plane
allocates a port from a range specified by `--service-node-port-range` flag (default: 30000-32767).