From cc241d97cef8e322da65c660517e196d3979cec5 Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Sun, 8 May 2022 10:21:54 -0400 Subject: [PATCH] Updating page per feedback from QA --- content/rancher/v2.6/en/neuvector-integration/_index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/rancher/v2.6/en/neuvector-integration/_index.md b/content/rancher/v2.6/en/neuvector-integration/_index.md index 5082c3b844f..2efefea8934 100644 --- a/content/rancher/v2.6/en/neuvector-integration/_index.md +++ b/content/rancher/v2.6/en/neuvector-integration/_index.md @@ -104,17 +104,17 @@ Below are the minimum recommended computing resources for the NeuVector chart in * NeuVector is not supported on a Windows cluster. -* Hardened cluster NeuVector installation is not supported. +* NeuVector installation is not supported on hardened clusters. -* SELinux clusters are not supported. +* NeuVector installation is not supported on SELinux clusters. -* Airgap is not supported. +* NeuVector installation is not supported on clusters in an air-gapped environment. ### Other Limitations * Currently, NeuVector feature chart installation fails when a NeuVector partner chart already exists. To work around this issue, uninstall the NeuVector partner chart and reinstall the NeuVector feature chart. -* Users cannot access the NeuVector UI from Rancher for a custom RKE1 cluster. To work around this, restart the controllers; note that while the controller pods are restarting, it will take additional time for the controller pods to become active. +* Sometimes when the controllers are not ready, the NeuVector UI is not accessible from the Rancher UI. During this time, controllers will try to restart, and it takes a few minutes for the controllers to be active. * Container runtime is not auto-detected for different cluster types when installing the NeuVector chart.