This message was deleted.
# rke2a
adamant-kite-43734
07/11/2024, 9:38 AMThis message was deleted.
s
salmon-morning-84088
07/11/2024, 11:32 AMGot a partial answer by trying it out. I'm getting this error if using the bootstrap token as credentials:
panic: failed to normalize server token; must be in format K10<CA-HASH>::<USERNAME>:<PASSWORD> or <PASSWORD>servers
sparse-fireman-14239
07/11/2024, 2:35 PMIt's arbitrary, the token can be whatever you like
😕 1
c
creamy-pencil-82913
07/11/2024, 4:53 PMcreamy-pencil-82913
07/11/2024, 4:53 PMThe secure token format (occasionally referred to as a “full” token) contains the following parts:
<prefix><cluster CA hash>::<credentials>
• `prefix`: a fixedprefix that identifies the token formatK10
• `cluster CA hash`: The hash of the cluster’s server CA certificate, used to authenticate the server to the joining node.
◦ For self-signed CA certificates, this is the SHA256 sum of the PEM-formatted certificate, as stored on disk.
◦ For custom CA certificates, this is the SHA256 sum of the DER encoding of the root certificate; commonly known as the certificate fingerprint.
• `credentials`: The username and password, or bearer token, used to authenticate the joining node to the cluster.
creamy-pencil-82913
07/11/2024, 4:55 PMthe username needs to be server for the server token, and node for the agent token. If you are using bootstrap tokens, there is no username portion, because it uses it as a bearer token instead of basic auth credential
👍 1
145 Views