From 80b114cdd770f475890dae03fa8ddf9fc5508189 Mon Sep 17 00:00:00 2001 From: Bastian Hofmann Date: Fri, 15 Oct 2021 17:37:51 +0200 Subject: [PATCH] Simplify docs to install Istio on RKE2 with selinux Signed-off-by: Bastian Hofmann --- .../istio/configuration-reference/rke2/_index.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/content/rancher/v2.6/en/istio/configuration-reference/rke2/_index.md b/content/rancher/v2.6/en/istio/configuration-reference/rke2/_index.md index a59cfdee6c4..03615c85b63 100644 --- a/content/rancher/v2.6/en/istio/configuration-reference/rke2/_index.md +++ b/content/rancher/v2.6/en/istio/configuration-reference/rke2/_index.md @@ -16,9 +16,17 @@ When installing or upgrading the Istio Helm chart through **Apps & Marketplace,* components: cni: enabled: true + k8s: + overlays: + - apiVersion: "apps/v1" + kind: "DaemonSet" + name: "istio-cni-node" + patches: + - path: spec.template.spec.containers.[name:install-cni].securityContext.privileged + value: true values: cni: - image: rancher/istio-install-cni:1.7.3 + image: rancher/mirrored-istio-install-cni:1.9.3 excludeNamespaces: - istio-system - kube-system @@ -26,10 +34,5 @@ When installing or upgrading the Istio Helm chart through **Apps & Marketplace,* cniBinDir: /opt/cni/bin cniConfDir: /etc/cni/net.d ``` -1. After installing or upgrading Istio, you'll notice the cni-node pods in the istio-system namespace in a CrashLoopBackoff error. Manually edit the `istio-cni-node` daemonset to include the following on the `install-cni` container: - ```yaml - securityContext: - privileged: true - ``` **Result:** Now you should be able to utilize Istio as desired, including sidecar injection and monitoring via Kiali.