From f62e904391d5f76d94bac2278674f64ebbbe7b11 Mon Sep 17 00:00:00 2001 From: Tejeev Date: Tue, 20 May 2025 16:39:08 -0600 Subject: [PATCH 1/3] Re-added the ping test to he troubleshooting guide --- .../troubleshooting/other-troubleshooting-tips/networking.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/troubleshooting/other-troubleshooting-tips/networking.md b/docs/troubleshooting/other-troubleshooting-tips/networking.md index cf5874d0ddb..4c0efb72094 100644 --- a/docs/troubleshooting/other-troubleshooting-tips/networking.md +++ b/docs/troubleshooting/other-troubleshooting-tips/networking.md @@ -14,6 +14,11 @@ Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG Double check if all the [required ports](../../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md#networking-requirements) are opened in your (host) firewall. The overlay network uses UDP in comparison to all other required ports which are TCP. +## Check if your downstream node can communicate to Rancher Manager +Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the $RANCHER_URL as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successfully it should return `pong`. +``` +curl -k https://$RANCHER_URL/ping +``` ## Check if Overlay Network is Functioning Correctly From d2815b87071d6b45098d19f039c2bef9212c20cd Mon Sep 17 00:00:00 2001 From: Petr Kovar Date: Thu, 26 Jun 2025 21:01:10 +0200 Subject: [PATCH 2/3] Update docs/troubleshooting/other-troubleshooting-tips/networking.md --- docs/troubleshooting/other-troubleshooting-tips/networking.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/troubleshooting/other-troubleshooting-tips/networking.md b/docs/troubleshooting/other-troubleshooting-tips/networking.md index 4c0efb72094..aaf3534d9a1 100644 --- a/docs/troubleshooting/other-troubleshooting-tips/networking.md +++ b/docs/troubleshooting/other-troubleshooting-tips/networking.md @@ -15,7 +15,9 @@ Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG Double check if all the [required ports](../../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md#networking-requirements) are opened in your (host) firewall. The overlay network uses UDP in comparison to all other required ports which are TCP. ## Check if your downstream node can communicate to Rancher Manager -Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the $RANCHER_URL as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successfully it should return `pong`. + +Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the `$RANCHER_URL` as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successful, it should return `pong`. + ``` curl -k https://$RANCHER_URL/ping ``` From b15041642a36bcaef2baa83287cdf9350e8273e8 Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Fri, 1 May 2026 15:36:45 -0700 Subject: [PATCH 3/3] Port to other versions --- .../other-troubleshooting-tips/networking.md | 8 ++++++++ .../other-troubleshooting-tips/networking.md | 8 ++++++++ .../other-troubleshooting-tips/networking.md | 8 ++++++++ .../other-troubleshooting-tips/networking.md | 8 ++++++++ .../other-troubleshooting-tips/networking.md | 8 ++++++++ 5 files changed, 40 insertions(+) diff --git a/versioned_docs/version-2.10/troubleshooting/other-troubleshooting-tips/networking.md b/versioned_docs/version-2.10/troubleshooting/other-troubleshooting-tips/networking.md index cf5874d0ddb..598f1c4e307 100644 --- a/versioned_docs/version-2.10/troubleshooting/other-troubleshooting-tips/networking.md +++ b/versioned_docs/version-2.10/troubleshooting/other-troubleshooting-tips/networking.md @@ -15,6 +15,14 @@ Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG Double check if all the [required ports](../../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md#networking-requirements) are opened in your (host) firewall. The overlay network uses UDP in comparison to all other required ports which are TCP. +## Check if your downstream node can communicate to Rancher Manager + +Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the `$RANCHER_URL` as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successful, it should return `pong`. + +``` +curl -k https://$RANCHER_URL/ping +``` + ## Check if Overlay Network is Functioning Correctly The pod can be scheduled to any of the hosts you used for your cluster, but that means that the NGINX ingress controller needs to be able to route the request from `NODE_1` to `NODE_2`. This happens over the overlay network. If the overlay network is not functioning, you will experience intermittent TCP/HTTP connection failures due to the NGINX ingress controller not being able to route to the pod. diff --git a/versioned_docs/version-2.11/troubleshooting/other-troubleshooting-tips/networking.md b/versioned_docs/version-2.11/troubleshooting/other-troubleshooting-tips/networking.md index cf5874d0ddb..598f1c4e307 100644 --- a/versioned_docs/version-2.11/troubleshooting/other-troubleshooting-tips/networking.md +++ b/versioned_docs/version-2.11/troubleshooting/other-troubleshooting-tips/networking.md @@ -15,6 +15,14 @@ Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG Double check if all the [required ports](../../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md#networking-requirements) are opened in your (host) firewall. The overlay network uses UDP in comparison to all other required ports which are TCP. +## Check if your downstream node can communicate to Rancher Manager + +Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the `$RANCHER_URL` as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successful, it should return `pong`. + +``` +curl -k https://$RANCHER_URL/ping +``` + ## Check if Overlay Network is Functioning Correctly The pod can be scheduled to any of the hosts you used for your cluster, but that means that the NGINX ingress controller needs to be able to route the request from `NODE_1` to `NODE_2`. This happens over the overlay network. If the overlay network is not functioning, you will experience intermittent TCP/HTTP connection failures due to the NGINX ingress controller not being able to route to the pod. diff --git a/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/networking.md b/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/networking.md index cf5874d0ddb..598f1c4e307 100644 --- a/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/networking.md +++ b/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/networking.md @@ -15,6 +15,14 @@ Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG Double check if all the [required ports](../../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md#networking-requirements) are opened in your (host) firewall. The overlay network uses UDP in comparison to all other required ports which are TCP. +## Check if your downstream node can communicate to Rancher Manager + +Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the `$RANCHER_URL` as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successful, it should return `pong`. + +``` +curl -k https://$RANCHER_URL/ping +``` + ## Check if Overlay Network is Functioning Correctly The pod can be scheduled to any of the hosts you used for your cluster, but that means that the NGINX ingress controller needs to be able to route the request from `NODE_1` to `NODE_2`. This happens over the overlay network. If the overlay network is not functioning, you will experience intermittent TCP/HTTP connection failures due to the NGINX ingress controller not being able to route to the pod. diff --git a/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/networking.md b/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/networking.md index cf5874d0ddb..598f1c4e307 100644 --- a/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/networking.md +++ b/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/networking.md @@ -15,6 +15,14 @@ Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG Double check if all the [required ports](../../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md#networking-requirements) are opened in your (host) firewall. The overlay network uses UDP in comparison to all other required ports which are TCP. +## Check if your downstream node can communicate to Rancher Manager + +Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the `$RANCHER_URL` as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successful, it should return `pong`. + +``` +curl -k https://$RANCHER_URL/ping +``` + ## Check if Overlay Network is Functioning Correctly The pod can be scheduled to any of the hosts you used for your cluster, but that means that the NGINX ingress controller needs to be able to route the request from `NODE_1` to `NODE_2`. This happens over the overlay network. If the overlay network is not functioning, you will experience intermittent TCP/HTTP connection failures due to the NGINX ingress controller not being able to route to the pod. diff --git a/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/networking.md b/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/networking.md index cf5874d0ddb..598f1c4e307 100644 --- a/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/networking.md +++ b/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/networking.md @@ -15,6 +15,14 @@ Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG Double check if all the [required ports](../../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md#networking-requirements) are opened in your (host) firewall. The overlay network uses UDP in comparison to all other required ports which are TCP. +## Check if your downstream node can communicate to Rancher Manager + +Rancher components with HTTP endpoints generally contain a `ping` liveness probe which you can use to test connectivity. Replace the `$RANCHER_URL` as appropriate and run the following from a node to check that it has connectivity to Rancher Manager's servers in the `local` cluster. If successful, it should return `pong`. + +``` +curl -k https://$RANCHER_URL/ping +``` + ## Check if Overlay Network is Functioning Correctly The pod can be scheduled to any of the hosts you used for your cluster, but that means that the NGINX ingress controller needs to be able to route the request from `NODE_1` to `NODE_2`. This happens over the overlay network. If the overlay network is not functioning, you will experience intermittent TCP/HTTP connection failures due to the NGINX ingress controller not being able to route to the pod.