Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

How to properly set a predefined token with CA hash on server initialization? #10783

Closed
bglgwyng opened this issue Aug 30, 2024 · 0 comments
Closed

Comments

@bglgwyng
Copy link

bglgwyng commented Aug 30, 2024

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:

  1. Is it possible to set a complete token (including the CA hash) when starting a K3s server for the first time?

  2. 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!

@k3s-io k3s-io locked and limited conversation to collaborators Aug 30, 2024
@brandond brandond converted this issue into discussion #10788 Aug 30, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
Status: Done Issue
Development

No branches or pull requests

1 participant