-
Notifications
You must be signed in to change notification settings - Fork 383
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
Document how to "join" controllers when external etcd is used #4311
Comments
As an adjacent observation, k0s allows join tokens for external MySQL or Postgres databases via kine. The situation for those storage types seems to be essentially the same as for external etcd. So I wonder if it would make more sense to simply allow join tokens for external etcd as well, or also refusing to create join tokens for any non-internal-etcd storage. |
IMO this would make sense |
The issue is marked as stale since no activity has been recorded in 30 days |
They are needed. Through the k0s join api, authorized via the token, the other controllers get the shared CA etc. files |
The issue is marked as stale since no activity has been recorded in 30 days |
The issue is marked as stale since no activity has been recorded in 30 days |
The issue is marked as stale since no activity has been recorded in 30 days |
Unless we document that in case of external etcd, one needs to copy over the CA etc files before booting the next controller. |
The issue is marked as stale since no activity has been recorded in 30 days |
The issue is marked as stale since no activity has been recorded in 30 days |
Wow, thanks for reporting the issue, I had the impression I was doing something wrong. Trying to enable verbose logging wasn't helpful as well. |
The issue is marked as stale since no activity has been recorded in 30 days |
@alemairebe Sorry, missed your comment. I've filed a k0sctl issue for that: k0sproject/k0sctl#825 |
When using external etcd, k0s refuses to create controller join tokens:
This is because join tokens aren't needed in this case. Just spin up another controller with the same config and that's it.
This needs to be documented somewhere, and the CLI error message might be more helpful. It might even include a link to the (not yet existing) documentation for this.
The text was updated successfully, but these errors were encountered: