From 09e95c09259ebb2bfefcfb93ccc6ebe2f25fdf5f Mon Sep 17 00:00:00 2001 From: David Shen Date: Sun, 27 Oct 2024 10:55:33 +1100 Subject: [PATCH] fix #345: add documentation for `--write-kubeconfig-group` option Signed-off-by: David Shen --- docs/cli/server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cli/server.md b/docs/cli/server.md index fa3918a1e..76ef29124 100644 --- a/docs/cli/server.md +++ b/docs/cli/server.md @@ -79,7 +79,7 @@ The following options must be set to the same value on all servers in the cluste |--------------------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `--write-kubeconfig value, -o` value | `K3S_KUBECONFIG_OUTPUT` | Write kubeconfig for admin client to this file | | `--write-kubeconfig-mode` value | `K3S_KUBECONFIG_MODE` | Write kubeconfig with this [mode.](https://en.wikipedia.org/wiki/Chmod) The kubeconfig file is owned by root, and written with a default mode of 600. Changing the mode to 644 will allow it to be read by other unprivileged users on the host. | - +| `--write-kubeconfig-group` value | `K3S_KUBECONFIG_GROUP` | Write kubeconfig group. Combining with `--write-kubeconfig-mode`, it will allow your k3s administrators accessing the kubeconfig file but keeping the file owned by root. | ## Advanced Options