From 350a30e6fc5ce8e5887bf7838644f961d8120717 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Wed, 16 Sep 2020 11:09:28 -0700 Subject: [PATCH] Say that K3s will fail to start if both new and deprecated SELinux flags are used Co-authored-by: Jacob Blain Christen --- content/k3s/latest/en/advanced/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/k3s/latest/en/advanced/_index.md b/content/k3s/latest/en/advanced/_index.md index 536d872a8e2..0ca39732d8f 100644 --- a/content/k3s/latest/en/advanced/_index.md +++ b/content/k3s/latest/en/advanced/_index.md @@ -314,7 +314,7 @@ rpm -i https://rpm.rancher.io/k3s-selinux-0.1.1-rc1.el7.noarch.rpm To force the install script to log a warning rather than fail, you can set the following environment variable: `INSTALL_K3S_SELINUX_WARN=true`. -The way that SELinux enforcement is enabled or disabled depends on the K3s version. +The way that SELinux enforcement is enabled or disabled depends on the K3s version. Prior to v1.19.x, SELinux enablement for the builtin containerd was automatic but could be disabled by passing `--disable-selinux`. With v1.19.x and beyond enabling SELinux must be affirmatively configured via the `--selinux` flag or config file entry. Servers and agents that specify both the `--selinux` and (deprecated) `--disable-selinux` flags will fail to start. {{% tabs %}} {{% tab "K3s v1.19.1+k3s1" %}}