Skip to content

Commit

Permalink
Remove warning (#1074)
Browse files Browse the repository at this point in the history
  • Loading branch information
@paigecalvert
paigecalvert authored Dec 12, 2024
1 parent e4a67ab commit 3e3f348
Showing 1 changed file with 0 additions and 4 deletions.
4 changes: 0 additions & 4 deletions src/markdown-pages/install-with-kurl/managing-nodes.md
View file
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

1 comment on commit 3e3f348

@github-actions
Copy link

Choose a reason for hiding this comment

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

🎉 Published on https://kurlsh-staging.netlify.app as production
🚀 Deployed on https://675b1b69b9c3c800d1288ea6--kurlsh-staging.netlify.app

Please sign in to comment.