From 7a513e6dee793a9498d2c02ab0168e7a9599e939 Mon Sep 17 00:00:00 2001 From: sandipanpanda <87253083+sandipanpanda@users.noreply.github.com> Date: Fri, 12 Nov 2021 21:32:28 +0530 Subject: [PATCH] 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 --- content/en/docs/concepts/configuration/overview.md | 2 +- content/en/docs/concepts/services-networking/ingress.md | 2 +- content/en/docs/concepts/services-networking/service.md | 2 +- .../tools/kubeadm/troubleshooting-kubeadm.md | 2 +- .../access-application-cluster/connecting-frontend-backend.md | 2 +- content/en/docs/tutorials/services/source-ip.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/concepts/configuration/overview.md b/content/en/docs/concepts/configuration/overview.md index 36eebe3abc..a4dd5c5901 100644 --- a/content/en/docs/concepts/configuration/overview.md +++ b/content/en/docs/concepts/configuration/overview.md @@ -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`. diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md index 6879b998db..3e2aeb6773 100644 --- a/content/en/docs/concepts/services-networking/ingress.md +++ b/content/en/docs/concepts/services-networking/ingress.md @@ -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 diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index 4f8eb45f38..cb3686dd21 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -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). diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md index d9f314ed4e..d0498b0c0d 100644 --- a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md +++ b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md @@ -159,7 +159,7 @@ Calico, Canal, and Flannel CNI providers are verified to support HostPort. For more information, see the [CNI portmap documentation](https://github.com/containernetworking/plugins/blob/master/plugins/meta/portmap/README.md). If your network provider does not support the portmap CNI plugin, you may need to use the [NodePort feature of -services](/docs/concepts/services-networking/service/#nodeport) or use `HostNetwork=true`. +services](/docs/concepts/services-networking/service/#type-nodeport) or use `HostNetwork=true`. ## Pods are not accessible via their Service IP diff --git a/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md b/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md index 9573a1a68d..37d27c7799 100644 --- a/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md +++ b/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md @@ -27,7 +27,7 @@ Kubernetes {{< glossary_tooltip term_id="service" >}} object. This task uses [Services with external load balancers](/docs/tasks/access-application-cluster/create-external-load-balancer/), which require a supported environment. If your environment does not support this, you can use a Service of type -[NodePort](/docs/concepts/services-networking/service/#nodeport) instead. +[NodePort](/docs/concepts/services-networking/service/#type-nodeport) instead. diff --git a/content/en/docs/tutorials/services/source-ip.md b/content/en/docs/tutorials/services/source-ip.md index 0a2d4b5929..a5b0d5a1d2 100644 --- a/content/en/docs/tutorials/services/source-ip.md +++ b/content/en/docs/tutorials/services/source-ip.md @@ -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