Support repair node from a disaster status, such as ip changed, system config changed, etc. #1414
Labels
command
sealer terminal command related
kind/feature
Category issues or PRs related to feature request
Issue Description
Type: feature request
Describe what feature you want
In some scenarios, due to some changes in the machine, such as IP changes, system configuration changes, etc., the K8s state of the node may be unavailable.
Similar to docker, if there is some problem with a container, using the (docker restart $container) command will actually reconfigure and restart the container without losing the persistent data, which can solve many misconfigure problems.
Therefore, I hope that sealer can also provide similar capabilities. When the above problems occur, simply executing a sealer restart command can correct the wrong configuration and repair the node to normal.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: