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

Detect conditions when workers need to be restarted or re-joined #722

Open
kke opened this issue May 30, 2024 · 1 comment
Open

Detect conditions when workers need to be restarted or re-joined #722

kke opened this issue May 30, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@kke
Copy link
Contributor

kke commented May 30, 2024

As mentioned by @twz123 in #721 (comment) - there are situations that could be consistently detected by k0sctl that require that the existing workers are restarted / reconfigured / rejoined.

This is something k0sctl should handle gracefully.

@kke
Copy link
Contributor Author

kke commented Dec 19, 2024

First and the most obvious is the change of externalAddress when a new token needs to be generated as the address is inside the token.

So, if that is detected, the service on the worker needs to be stopped, the two kubelet auth files need to be deleted and then a reinstall performed (which can be the regular InstallWorkers phase that now thinks there is no k0s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant