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
@@ -164,7 +164,7 @@ The `client_address` is always the client pod's IP address, whether the client p
## Source IP for Services with `Type=NodePort`
Packets sent to Services with
[`Type=NodePort`](/docs/concepts/services-networking/service/#nodeport)
[`Type=NodePort`](/docs/concepts/services-networking/service/#type-nodeport)
are source NAT'd by default. You can test this by creating a `NodePort` Service:
```shell