Skip to content

K
k3s
Switch branch/tag
  1. 26 Aug, 2022 1 commit
  3. 25 Aug, 2022 1 commit
  5. 23 Aug, 2022 2 commits
  7. 19 Aug, 2022 1 commit
  9. 18 Aug, 2022 1 commit
  11. 16 Aug, 2022 1 commit
  13. 15 Aug, 2022 2 commits
  15. 10 Aug, 2022 1 commit
  17. 08 Aug, 2022 1 commit
  19. 05 Aug, 2022 9 commits
  21. 04 Aug, 2022 3 commits
  23. 03 Aug, 2022 1 commit
  25. 02 Aug, 2022 2 commits
  27. 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
  29. 29 Jul, 2022 1 commit
  31. 28 Jul, 2022 2 commits
  33. 22 Jul, 2022 2 commits
  35. 21 Jul, 2022 8 commits