You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using default Sealos configurations for cluster setup.
With this config:
Default configuration with Kubernetes setup and basic network settings.
No custom modifications made to the Sealos configuration.
Run:
Run sealos reset --nodes 192.168.37.13 to reset only the node 192.168.37.13.
See error:
Instead of resetting just the node 192.168.37.13, the command resets the entire cluster, including master and other worker nodes. This behavior is not expected, as I only intended to reset the specified node.
What is the expected behavior?
I expect that when running sealos reset --nodes 192.168.37.13, only the node 192.168.37.13 should be reset, leaving the rest of the cluster (master and other worker nodes) intact.
What do you see instead?
Instead of resetting just the specified node 192.168.37.13, the entire cluster gets reset, including the master and other worker nodes, which is not the intended behavior.
Sealos Version
Sealos Version: 5.0.1
How to reproduce the bug?
In this environment:
With this config:
Run:
Run
sealos reset --nodes 192.168.37.13
to reset only the node192.168.37.13
.See error:
Instead of resetting just the node
192.168.37.13
, the command resets the entire cluster, including master and other worker nodes. This behavior is not expected, as I only intended to reset the specified node.What is the expected behavior?
I expect that when running
sealos reset --nodes 192.168.37.13
, only the node192.168.37.13
should be reset, leaving the rest of the cluster (master and other worker nodes) intact.What do you see instead?
Instead of resetting just the specified node
192.168.37.13
, the entire cluster gets reset, including the master and other worker nodes, which is not the intended behavior.Operating environment
Additional information
sealos reset --nodes
command, where the reset command affected the entire cluster instead of the specified node.The text was updated successfully, but these errors were encountered: