Skip to content
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.

Sign up for GitHub

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

Remove warning #1074

Merged
merged 1 commit into from
Dec 12, 2024
Merged

Remove warning #1074

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions src/markdown-pages/install-with-kurl/managing-nodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,10 +36,6 @@ Resetting a node can be useful if you are creating and testing a kURL specificat
Some larger changes to a kURL specification cannot be deployed for testing by rerunning the kURL installation script on an existing node.
In this case, you can attempt to reset the node so that you can reinstall kURL to test the change to the kURL specification.

_**Warning**_: Do not attempt to reset a node on a cluster in a production environment.
Attempting to reset a node can permanently damage the cluster, which makes any data from the cluster irretrievable.
Reset a node on a cluster only if you are able to delete the host VM and provision a new VM if the reset script does not successfully complete.

To reset a node on a cluster managed by kURL:

1. Run the kURL reset script on a VM that you are able to delete if the script is unsuccessful.
Expand Down