Skip to content

Re-added the ping test to he troubleshooting guide #1806

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Tejeev
Copy link
Contributor

@Tejeev Tejeev commented May 20, 2025

Fixes #1650

Reminders

  • See the README for more details on how to work with the Rancher docs.

  • Verify if changes pertain to other versions of Rancher. If they do, finalize the edits on one version of the page, then apply the edits to the other versions.

  • If the pull request is dependent on an upcoming release, remember to add a "MERGE ON RELEASE" label and set the proper milestone.

Description

Comments

Copy link
Contributor

@pmkovar pmkovar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR, just a few nitpicks.

@@ -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`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

I cant' find the basic troubleshooting steps for curling the rancher/ping endpoint
3 participants