From 2d431d73c9c2aa6d1fb3d0b33c7ce66e33cd89ff Mon Sep 17 00:00:00 2001 From: David Nuzik Date: Tue, 31 Mar 2020 14:06:41 -0700 Subject: [PATCH] Address symlink issue on installation-requirements page - Resolves symlink issue in single-server section of https://github.com/rancher/k3s/issues/1031 - The INSTALL_K3S_SYMLINK env var now has a description that explains what binaries symlinks are created for --- content/k3s/latest/en/installation/install-options/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/k3s/latest/en/installation/install-options/_index.md b/content/k3s/latest/en/installation/install-options/_index.md index e2bc4a2dbb2..d8c415cb96c 100644 --- a/content/k3s/latest/en/installation/install-options/_index.md +++ b/content/k3s/latest/en/installation/install-options/_index.md @@ -29,7 +29,7 @@ When using this method to install K3s, the following environment variables can b - `INSTALL_K3S_SYMLINK` - If set to 'skip' will not create symlinks, 'force' will overwrite, default will symlink if command does not exist in path. + By default will create symlinks for the kubectl, crictl, and ctr binaries if the commands do not already exist in path. If set to 'skip' will not create symlinks and 'force' will overwrite. - `INSTALL_K3S_SKIP_START`