From f62e904391d5f76d94bac2278674f64ebbbe7b11 Mon Sep 17 00:00:00 2001 From: Tejeev Date: Tue, 20 May 2025 16:39:08 -0600 Subject: [PATCH] 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