Skip to content

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.

@btat btat added the port/community-product Triggers a GitHub action to file a community sync issue for rancher-product-docs. label Jun 5, 2025
@pmkovar
Copy link
Contributor

pmkovar commented Jun 26, 2025

@Tejeev This applies to all supported Rancher versions, correct? If so, we need to update the versioned docs files as well.

@Tejeev
Copy link
Contributor Author

Tejeev commented Oct 17, 2025

@pmkovar last I checked every tool we create in Rancher has this functionality and always has.

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

Labels

port/community-product Triggers a GitHub action to file a community sync issue for rancher-product-docs.

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