From 53ed57efe36850ae77c88b860a1567b0408452f6 Mon Sep 17 00:00:00 2001 From: Erik Wilson Date: Wed, 20 Nov 2019 13:40:46 -0700 Subject: [PATCH] Update k3s v1.0.0 Node Registration information --- content/k3s/latest/en/configuration/_index.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/k3s/latest/en/configuration/_index.md b/content/k3s/latest/en/configuration/_index.md index b1b5ece6f97..1f3cc7d7bf8 100644 --- a/content/k3s/latest/en/configuration/_index.md +++ b/content/k3s/latest/en/configuration/_index.md @@ -96,10 +96,11 @@ Node Registration ----------------- Agents will register with the server using the node cluster secret along with a randomly generated -password for the node, stored at `/var/lib/rancher/k3s/agent/node-password.txt`. The server will +password for the node, stored at `/etc/rancher/node/password`. The server will store the passwords for individual nodes at `/var/lib/rancher/k3s/server/cred/node-passwd`, and any -subsequent attempts must use the same password. If the data directory of an agent is removed the -password file should be recreated for the agent, or the entry removed from the server. +subsequent attempts must use the same password. If the `/etc/rancher/node` directory of an agent is removed the +password file should be recreated for the agent, or the entry removed from the server. A unique node +id can be appended to the hostname by launching k3s servers or agents using the `--with-node-id` flag. Containerd and Docker ----------