diff --git a/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md b/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md index f2354ec4c59..b30d980d1ac 100644 --- a/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md +++ b/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md @@ -7,7 +7,7 @@ description: Ingress configuration For Kubernetes v1.21 and up, the NGINX Ingress controller no longer runs in hostNetwork by default. It instead uses hostPorts for port 80 and port 443, so you can configure the admission webhook to be accessible only through the ClusterIP. This ensures that the webhook is only accessible from within the cluster. -Because of this change to the controller, the default behavior no longer sets `hostNetwork` to `true`. However, you must set `hostNetwork` to `true` for TCP- and UDP-based Services to work. +Because of this change to the controller, the default behavior no longer sets `hostNetwork` to `true`. However, you must [set `hostNetwork` to `true`](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options) for TCP- and UDP-based Services to work. To do so, [edit the cluster's YAML](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration.md#editing-clusters-with-yaml) and follow the [instructions](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options) described in the official RKE docs. ::: diff --git a/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md b/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md index 8a2aabbeea0..398e239ee1e 100644 --- a/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md +++ b/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md @@ -7,7 +7,7 @@ description: Ingress configuration For Kubernetes v1.21 and up, the NGINX Ingress controller no longer runs in hostNetwork by default. It instead uses hostPorts for port 80 and port 443, so you can configure the admission webhook to be accessible only through the ClusterIP. This ensures that the webhook is only accessible from within the cluster. -Because of this change to the controller, the default behavior no longer sets `hostNetwork` to `true`. However, you must set `hostNetwork` to `true` for TCP- and UDP-based Services to work. +Because of this change to the controller, the default behavior no longer sets `hostNetwork` to `true`. However, you must [set `hostNetwork` to `true`](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options) for TCP- and UDP-based Services to work. To do so, [edit the cluster's YAML](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration.md#editing-clusters-with-yaml) and follow the [instructions](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options) described in the official RKE docs. ::: diff --git a/versioned_docs/version-2.7/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md b/versioned_docs/version-2.7/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md index f2354ec4c59..b30d980d1ac 100644 --- a/versioned_docs/version-2.7/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md +++ b/versioned_docs/version-2.7/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md @@ -7,7 +7,7 @@ description: Ingress configuration For Kubernetes v1.21 and up, the NGINX Ingress controller no longer runs in hostNetwork by default. It instead uses hostPorts for port 80 and port 443, so you can configure the admission webhook to be accessible only through the ClusterIP. This ensures that the webhook is only accessible from within the cluster. -Because of this change to the controller, the default behavior no longer sets `hostNetwork` to `true`. However, you must set `hostNetwork` to `true` for TCP- and UDP-based Services to work. +Because of this change to the controller, the default behavior no longer sets `hostNetwork` to `true`. However, you must [set `hostNetwork` to `true`](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options) for TCP- and UDP-based Services to work. To do so, [edit the cluster's YAML](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration.md#editing-clusters-with-yaml) and follow the [instructions](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options) described in the official RKE docs. :::