From 547fbfa73d40a03a1ec603e6791ad99a7f3a3192 Mon Sep 17 00:00:00 2001 From: martyav Date: Wed, 19 Jul 2023 17:36:20 -0400 Subject: [PATCH 1/4] #455 How to set hostNetwork:true for k8s 1.21 and up --- .../ingress-configuration.md | 2 +- .../ingress-configuration.md | 2 +- .../ingress-configuration.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) 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. ::: From d792957d51c082634250d09cf8307f122b6c1731 Mon Sep 17 00:00:00 2001 From: martyav Date: Wed, 19 Jul 2023 17:42:40 -0400 Subject: [PATCH 2/4] rm'd duplicate link --- .../ingress-configuration.md | 2 +- .../ingress-configuration.md | 2 +- .../ingress-configuration.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) 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 b30d980d1ac..8c5f214cf45 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`](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. +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. 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 398e239ee1e..5eb74ad9b07 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`](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. +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. 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 b30d980d1ac..8c5f214cf45 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`](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. +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. 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. ::: From 03e45f55286851608d5945c61618a5600028567b Mon Sep 17 00:00:00 2001 From: martyav Date: Fri, 21 Jul 2023 10:38:14 -0400 Subject: [PATCH 3/4] instructions for rke and rke2 --- .../ingress-configuration.md | 2 +- .../ingress-configuration.md | 2 +- .../ingress-configuration.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) 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 8c5f214cf45..423618e922f 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. 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. +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. To do so, edit the cluster's YAML ([RKE2 instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration.md#editing-clusters-with-yaml)/[RKE instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml)) and follow the steps in the [official RKE doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options). ::: 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 5eb74ad9b07..479230f1e3b 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. 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. +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. To do so, edit the cluster's YAML ([RKE2 instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration.md#editing-clusters-with-yaml)/[RKE instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml)) and follow the steps in the [official RKE doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options). ::: 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 8c5f214cf45..423618e922f 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. 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. +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. To do so, edit the cluster's YAML ([RKE2 instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration.md#editing-clusters-with-yaml)/[RKE instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml)) and follow the steps in the [official RKE doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options). ::: From 106f9d179addfaa863fa631990d5ab8c36fe57bc Mon Sep 17 00:00:00 2001 From: martyav Date: Thu, 10 Aug 2023 15:42:02 -0400 Subject: [PATCH 4/4] rm'd mention of rke2 --- .../ingress-configuration.md | 2 +- .../ingress-configuration.md | 3 ++- .../ingress-configuration.md | 3 ++- 3 files changed, 5 insertions(+), 3 deletions(-) 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 423618e922f..63747c686c0 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. To do so, edit the cluster's YAML ([RKE2 instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration.md#editing-clusters-with-yaml)/[RKE instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml)) and follow the steps in the [official RKE doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options). +Because of this change to the controller, the default RKE1 behavior no longer sets `hostNetwork` to `true`. However, you must set `hostNetwork` to `true` for TCP- and UDP-based Services to work. To do so, [edit](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml) the cluster's YAML and follow the steps in the [official RKE1 doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options). ::: 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 479230f1e3b..86a3f3d6360 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,8 @@ 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. To do so, edit the cluster's YAML ([RKE2 instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration.md#editing-clusters-with-yaml)/[RKE instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml)) and follow the steps in the [official RKE doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options). +Because of this change to the controller, the default RKE1 behavior no longer sets `hostNetwork` to `true`. However, you must set `hostNetwork` to `true` for TCP- and UDP-based Services to work. To do so, [edit](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml) the cluster's YAML and follow the steps in the [official RKE1 doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options). + ::: 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 423618e922f..670484ac32c 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,8 @@ 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. To do so, edit the cluster's YAML ([RKE2 instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration.md#editing-clusters-with-yaml)/[RKE instructions](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml)) and follow the steps in the [official RKE doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options). +Because of this change to the controller, the default RKE1 behavior no longer sets `hostNetwork` to `true`. However, you must set `hostNetwork` to `true` for TCP- and UDP-based Services to work. To do so, [edit](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml) the cluster's YAML and follow the steps in the [official RKE1 doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options). + :::