Skip to content

K
k3s
Switch branch/tag
  1. 27 Aug, 2022 1 commit
  3. 26 Aug, 2022 5 commits
  5. 25 Aug, 2022 1 commit
  7. 23 Aug, 2022 2 commits
  9. 19 Aug, 2022 1 commit
  11. 18 Aug, 2022 1 commit
  13. 16 Aug, 2022 1 commit
  15. 15 Aug, 2022 2 commits
  17. 10 Aug, 2022 1 commit
  19. 08 Aug, 2022 1 commit
  21. 05 Aug, 2022 9 commits
  23. 04 Aug, 2022 3 commits
  25. 03 Aug, 2022 1 commit
  27. 02 Aug, 2022 2 commits
  29. 01 Aug, 2022 1 commit
    • Vladimir Kochnev's avatar
      Save agent token to /var/lib/rancher/k3s/server/agent-token · 13af0b1d
      Vladimir Kochnev authored 
      Having separate tokens for server and agent nodes is a nice feature.

However, passing server's plain `K3S_AGENT_TOKEN` value
to `k3s agent --token` without CA hash is insecure when CA is
self-signed, and k3s warns about it in the logs:

```
Cluster CA certificate is not trusted by the host CA bundle, but the token does not include a CA hash.
Use the full token from the server's node-token file to enable Cluster CA validation.
```

Okay so I need CA hash but where should I get it?

This commit attempts to fix this issue by saving agent token value to
`agent-token` file with CA hash appended.
Signed-off-by: 's avatarVladimir Kochnev <hashtable@yandex.ru>
      13af0b1d
  31. 29 Jul, 2022 1 commit
  33. 28 Jul, 2022 2 commits
  35. 22 Jul, 2022 2 commits
  37. 21 Jul, 2022 3 commits