mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 04:28:15 +00:00
Removing ingress-nginx due to deprecation and replacing with traefik.
Signed-off-by: Sunil Singh <sunil.singh@suse.com>
This commit is contained in:
+1
-1
@@ -45,7 +45,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -56,6 +55,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
kind: PodSecurityConfiguration
|
||||
name: PodSecurity
|
||||
path: ""
|
||||
|
||||
+1
-1
@@ -121,7 +121,6 @@ When you run Rancher on a Kubernetes cluster that enforces a restrictive securit
|
||||
- `compliance-operator-system`
|
||||
- `fleet-default`
|
||||
- `fleet-local`
|
||||
- `ingress-nginx`
|
||||
- `istio-system`
|
||||
- `kube-node-lease`
|
||||
- `kube-public`
|
||||
@@ -132,6 +131,7 @@ When you run Rancher on a Kubernetes cluster that enforces a restrictive securit
|
||||
- `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).
|
||||
|
||||
|
||||
@@ -58,7 +58,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -69,6 +68,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
runtimeClasses: []
|
||||
usernames: []
|
||||
```
|
||||
|
||||
+1
-1
@@ -45,7 +45,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -56,6 +55,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
kind: PodSecurityConfiguration
|
||||
name: PodSecurity
|
||||
path: ""
|
||||
|
||||
+1
-1
@@ -120,7 +120,6 @@ The policies shipped by default in Rancher aim to provide a trade-off between se
|
||||
- `compliance-operator-system`
|
||||
- `fleet-default`
|
||||
- `fleet-local`
|
||||
- `ingress-nginx`
|
||||
- `istio-system`
|
||||
- `kube-node-lease`
|
||||
- `kube-public`
|
||||
@@ -131,6 +130,7 @@ The policies shipped by default in Rancher aim to provide a trade-off between se
|
||||
- `security-scan`
|
||||
- `sr-operator-system`
|
||||
- `tigera-operator`
|
||||
- `traefik`
|
||||
|
||||
Rancher、Rancher 拥有的一些 Chart 以及 RKE2 和 K3s 发行版都使用这些命名空间。列出的命名空间的一个子集已经在内置的 Rancher `rancher-restricted` 策略中被豁免,用于下游集群。有关运行 Rancher 所需的所有豁免的完整模板,请参阅此[准入配置示例](../../../reference-guides/rancher-security/psa-restricted-exemptions.md)。
|
||||
|
||||
|
||||
+1
-1
@@ -54,7 +54,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -65,6 +64,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
runtimeClasses: []
|
||||
usernames: []
|
||||
```
|
||||
|
||||
+1
-1
@@ -45,7 +45,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -56,6 +55,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
kind: PodSecurityConfiguration
|
||||
name: PodSecurity
|
||||
path: ""
|
||||
|
||||
+1
-1
@@ -120,7 +120,6 @@ The policies shipped by default in Rancher aim to provide a trade-off between se
|
||||
- `compliance-operator-system`
|
||||
- `fleet-default`
|
||||
- `fleet-local`
|
||||
- `ingress-nginx`
|
||||
- `istio-system`
|
||||
- `kube-node-lease`
|
||||
- `kube-public`
|
||||
@@ -131,6 +130,7 @@ The policies shipped by default in Rancher aim to provide a trade-off between se
|
||||
- `security-scan`
|
||||
- `sr-operator-system`
|
||||
- `tigera-operator`
|
||||
- `traefik`
|
||||
|
||||
Rancher、Rancher 拥有的一些 Chart 以及 RKE2 和 K3s 发行版都使用这些命名空间。列出的命名空间的一个子集已经在内置的 Rancher `rancher-restricted` 策略中被豁免,用于下游集群。有关运行 Rancher 所需的所有豁免的完整模板,请参阅此[准入配置示例](../../../reference-guides/rancher-security/psa-restricted-exemptions.md)。
|
||||
|
||||
|
||||
+1
-1
@@ -54,7 +54,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -65,6 +64,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
runtimeClasses: []
|
||||
usernames: []
|
||||
```
|
||||
|
||||
+1
-1
@@ -45,7 +45,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -56,6 +55,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
kind: PodSecurityConfiguration
|
||||
name: PodSecurity
|
||||
path: ""
|
||||
|
||||
+1
-1
@@ -120,7 +120,6 @@ The policies shipped by default in Rancher aim to provide a trade-off between se
|
||||
- `compliance-operator-system`
|
||||
- `fleet-default`
|
||||
- `fleet-local`
|
||||
- `ingress-nginx`
|
||||
- `istio-system`
|
||||
- `kube-node-lease`
|
||||
- `kube-public`
|
||||
@@ -131,6 +130,7 @@ The policies shipped by default in Rancher aim to provide a trade-off between se
|
||||
- `security-scan`
|
||||
- `sr-operator-system`
|
||||
- `tigera-operator`
|
||||
- `traefik`
|
||||
|
||||
Rancher、Rancher 拥有的一些 Chart 以及 RKE2 和 K3s 发行版都使用这些命名空间。列出的命名空间的一个子集已经在内置的 Rancher `rancher-restricted` 策略中被豁免,用于下游集群。有关运行 Rancher 所需的所有豁免的完整模板,请参阅此[准入配置示例](../../../reference-guides/rancher-security/psa-restricted-exemptions.md)。
|
||||
|
||||
|
||||
+1
-1
@@ -54,7 +54,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -65,6 +64,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
runtimeClasses: []
|
||||
usernames: []
|
||||
```
|
||||
|
||||
+1
-1
@@ -45,7 +45,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -56,6 +55,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
kind: PodSecurityConfiguration
|
||||
name: PodSecurity
|
||||
path: ""
|
||||
|
||||
+1
-1
@@ -121,7 +121,6 @@ When you run Rancher on a Kubernetes cluster that enforces a restrictive securit
|
||||
- `compliance-operator-system`
|
||||
- `fleet-default`
|
||||
- `fleet-local`
|
||||
- `ingress-nginx`
|
||||
- `istio-system`
|
||||
- `kube-node-lease`
|
||||
- `kube-public`
|
||||
@@ -132,6 +131,7 @@ When you run Rancher on a Kubernetes cluster that enforces a restrictive securit
|
||||
- `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).
|
||||
|
||||
|
||||
+1
-1
@@ -58,7 +58,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -69,6 +68,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
runtimeClasses: []
|
||||
usernames: []
|
||||
```
|
||||
|
||||
+1
-1
@@ -45,7 +45,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -56,6 +55,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
kind: PodSecurityConfiguration
|
||||
name: PodSecurity
|
||||
path: ""
|
||||
|
||||
+1
-1
@@ -121,7 +121,6 @@ When you run Rancher on a Kubernetes cluster that enforces a restrictive securit
|
||||
- `compliance-operator-system`
|
||||
- `fleet-default`
|
||||
- `fleet-local`
|
||||
- `ingress-nginx`
|
||||
- `istio-system`
|
||||
- `kube-node-lease`
|
||||
- `kube-public`
|
||||
@@ -132,6 +131,7 @@ When you run Rancher on a Kubernetes cluster that enforces a restrictive securit
|
||||
- `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).
|
||||
|
||||
|
||||
+1
-1
@@ -58,7 +58,6 @@ plugins:
|
||||
- compliance-operator-system
|
||||
- fleet-default
|
||||
- fleet-local
|
||||
- ingress-nginx
|
||||
- istio-system
|
||||
- kube-node-lease
|
||||
- kube-public
|
||||
@@ -69,6 +68,7 @@ plugins:
|
||||
- security-scan
|
||||
- sr-operator-system
|
||||
- tigera-operator
|
||||
- traefik
|
||||
runtimeClasses: []
|
||||
usernames: []
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user