Custom token in config.yaml ignored when bootstrapping new cluster with cluster-init

[scaljeri]

I am bootstrapping a brand new K3s cluster using /etc/rancher/k3s/config.yaml with:

  cluster-init: true
  node-ip: 192.168.2.220
  tls-san:
    - 192.168.2.220
  token: "<my-custom-token>"

I then install using: curl -sfL https://get.k3s.io | sh -s - server

The cluster starts successfully, but the generated token in /var/lib/rancher/k3s/server/token is different from the one I defined in config.yaml. It appears that the custom token is ignored when bootstrapping a new cluster with cluster-init: true.

Is this expected behavior? If not, what would cause K3s to override the provided token during initial cluster creation?

Thnx

[brandond]

Are you sure it's actually different, and you're not just seeing the cluster CA hash prepended to the token you specified?

See the docs on token types.

[scaljeri]

You're right, I expected to be the whole token, but its just the last part. And I noticed I can join nodes with just . Sorry, my mistake!