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.

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

Support repair node from a disaster status, such as ip changed, system config changed, etc. #1414

Open
VinceCui opened this issue May 17, 2022 · 0 comments
Labels
command sealer terminal command related kind/feature Category issues or PRs related to feature request

Comments

@VinceCui
Copy link
Collaborator

VinceCui commented May 17, 2022

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.

@VinceCui VinceCui added kind/feature Category issues or PRs related to feature request command sealer terminal command related labels May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
command sealer terminal command related kind/feature Category issues or PRs related to feature request
Projects
None yet
Development

No branches or pull requests

1 participant