From befe490e2cfee259536684620c65eca90c9196e7 Mon Sep 17 00:00:00 2001 From: Nelson Roberts Date: Thu, 26 Mar 2020 16:33:20 -0700 Subject: [PATCH] Rancher-26175: add known issues with hardened cluster --- content/rancher/v2.x/en/security/hardening-2.3.5/_index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/rancher/v2.x/en/security/hardening-2.3.5/_index.md b/content/rancher/v2.x/en/security/hardening-2.3.5/_index.md index 213826808ad..75a48a7ba50 100644 --- a/content/rancher/v2.x/en/security/hardening-2.3.5/_index.md +++ b/content/rancher/v2.x/en/security/hardening-2.3.5/_index.md @@ -22,6 +22,10 @@ This document provides prescriptive guidance for hardening a production installa For more detail about evaluating a hardened cluster against the official CIS benchmark, refer to the [CIS Benchmark Rancher Self-Assessment Guide - Rancher v2.3.5]({{< baseurl >}}/rancher/v2.x/en/security/benchmark-2.3.5/). +#### Known Issues + +Rancher **exec shell** and **view logs** for pods are **not** functional in a cis 1.5 hardened setup when only public ip is provided when registering custom nodes. + ### Configure Kernel Runtime Parameters The following `sysctl` configuration is recommended for all nodes type in the cluster. Set the following parameters in `/etc/sysctl.d/90-kubelet.conf`: