1. 22 Sep, 2022 1 commit
  2. 16 Sep, 2022 1 commit
  3. 10 Sep, 2022 3 commits
  4. 06 Sep, 2022 1 commit
  5. 02 Sep, 2022 3 commits
  6. 26 Aug, 2022 5 commits
  7. 25 Aug, 2022 1 commit
  8. 23 Aug, 2022 2 commits
  9. 19 Aug, 2022 1 commit
  10. 18 Aug, 2022 1 commit
  11. 16 Aug, 2022 1 commit
  12. 15 Aug, 2022 2 commits
  13. 10 Aug, 2022 1 commit
  14. 08 Aug, 2022 1 commit
  15. 05 Aug, 2022 9 commits
  16. 04 Aug, 2022 3 commits
  17. 03 Aug, 2022 1 commit
  18. 02 Aug, 2022 2 commits
  19. 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