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
I'm trying to set up a K3s server with a predefined token, including the CA hash, during the initialization process. I understand that the token format should be K10<random-string>::<ca-hash>, but I'm unsure how to generate this correctly before the server starts.
Specifically:
Is it possible to set a complete token (including the CA hash) when starting a K3s server for the first time?
If not, what's the recommended way to set a predefined random part of the token (<prefix><cluster CA hash>::<credentials>) and have K3s append the correct CA hash on initialization? It doesn't seem that we can configure CA certificates k3s to use. So it seems impossible to set CA hash on initialization, is it correct?
I'm working with a NixOS configuration, but I'm interested in the general approach that would work for any system.
Thank you for your help and for maintaining this great project!
The text was updated successfully, but these errors were encountered:
I'm trying to set up a K3s server with a predefined token, including the CA hash, during the initialization process. I understand that the token format should be
K10<random-string>::<ca-hash>
, but I'm unsure how to generate this correctly before the server starts.Specifically:
Is it possible to set a complete token (including the CA hash) when starting a K3s server for the first time?
If not, what's the recommended way to set a predefined random part of the token (
<prefix><cluster CA hash>::<credentials>
) and have K3s append the correct CA hash on initialization? It doesn't seem that we can configure CA certificates k3s to use. So it seems impossible to set CA hash on initialization, is it correct?I'm working with a NixOS configuration, but I'm interested in the general approach that would work for any system.
Thank you for your help and for maintaining this great project!
The text was updated successfully, but these errors were encountered: