Merge pull request #2224 from sunilarjun/update-ns

Updating ns exemptions

versioned_docs/version-2.13/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/psa-config-templates.md

@@ -91,6 +91,7 @@ When you run Rancher on a Kubernetes cluster that enforces a restrictive securit
 - `calico-apiserver`
 - `calico-system`
 - `cattle-alerting`
+- `cattle-capi-system`
 - `cattle-csp-adapter-system`
 - `cattle-elemental-system`
 - `cattle-epinio-system`
@@ -112,22 +113,25 @@ When you run Rancher on a Kubernetes cluster that enforces a restrictive securit
 - `cattle-resources-system`
 - `cattle-sriov-system`
 - `cattle-system`
+- `cattle-turtles-system`
 - `cattle-ui-plugin-system`
 - `cattle-windows-gmsa-system`
 - `cert-manager`
 - `cis-operator-system`
+- `compliance-operator-system`
 - `fleet-default`
 - `fleet-local`
-- `ingress-nginx`
 - `istio-system`
 - `kube-node-lease`
 - `kube-public`
 - `kube-system`
 - `longhorn-system`
 - `rancher-alerting-drivers`
+- `rancher-compliance-system`
 - `security-scan`
 - `sr-operator-system`
 - `tigera-operator`
+- `traefik`
 
 Rancher, some Rancher owned charts, and RKE2 and K3s distributions all use these namespaces. A subset of the listed namespaces are already exempt in the built-in Rancher `rancher-restricted` policy, for use in downstream clusters. For a complete template which has all the exemptions you need to run Rancher, please refer to this [sample Admission Configuration](../../../reference-guides/rancher-security/psa-restricted-exemptions.md).