Remove s390x references (#388)

* Remove s390x references

Signed-off-by: Derek Nola <derek.nola@suse.com>

* Remove dead link

Signed-off-by: Derek Nola <derek.nola@suse.com>

---------

Signed-off-by: Derek Nola <derek.nola@suse.com>

Author: dereknola

docs/installation/requirements.md

@@ -18,7 +18,6 @@ K3s is available for the following architectures:
 - x86_64
 - armhf
 - arm64/aarch64
-- s390x
 
 :::warning ARM64 Page Size
 
@@ -169,7 +168,7 @@ The VXLAN port on nodes should not be exposed to the world as it opens up your c
 :::
 
 :::danger
-Flannel relies on the [Bridge CNI plugin](https://www.cni.dev/plugins/current/main/bridge/) to create a L2 network that switches traffic. Rogue pods with `NET_RAW` capabilities can abuse that L2 network to launch attacks such as [ARP spoofing](https://static.sched.com/hosted_files/kccncna19/72/ARP%20DNS%20spoof.pdf). Therefore, as documented in the [Kubernetes docs](https://kubernetes.io/docs/concepts/security/pod-security-standards/), please set a restricted profile that disables `NET_RAW` on non-trustable pods.
+Flannel relies on the [Bridge CNI plugin](https://www.cni.dev/plugins/current/main/bridge/) to create a L2 network that switches traffic. Rogue pods with `NET_RAW` capabilities can abuse that L2 network to launch attacks such as ARP spoofing. Therefore, as documented in the [Kubernetes docs](https://kubernetes.io/docs/concepts/security/pod-security-standards/), please set a restricted profile that disables `NET_RAW` on non-trustable pods.
 :::
 
 ### Inbound Rules for K3s Nodes

i18n/ja/docusaurus-plugin-content-docs/current/installation/requirements.md

@@ -18,7 +18,6 @@ K3sは以下のアーキテクチャで利用可能です:
 - x86_64
 - armhf
 - arm64/aarch64
-- s390x
 
 :::warning ARM64 ページサイズ
 

i18n/kr/docusaurus-plugin-content-docs/current/installation/requirements.md

@@ -18,7 +18,6 @@ K3s is available for the following architectures:
 - x86_64
 - armhf
 - arm64/aarch64
-- s390x
 
 :::warning ARM64 Page Size
 
@@ -127,7 +126,7 @@ The VXLAN port on nodes should not be exposed to the world as it opens up your c
 :::
 
 :::danger
-Flannel relies on the [Bridge CNI plugin](https://www.cni.dev/plugins/current/main/bridge/) to create a L2 network that switches traffic. Rogue pods with `NET_RAW` capabilities can abuse that L2 network to launch attacks such as [ARP spoofing](https://static.sched.com/hosted_files/kccncna19/72/ARP%20DNS%20spoof.pdf). Therefore, as documented in the [Kubernetes docs](https://kubernetes.io/docs/concepts/security/pod-security-standards/), please set a restricted profile that disables `NET_RAW` on non-trustable pods.
+Flannel relies on the [Bridge CNI plugin](https://www.cni.dev/plugins/current/main/bridge/) to create a L2 network that switches traffic. Rogue pods with `NET_RAW` capabilities can abuse that L2 network to launch attacks such as ARP spoofing. Therefore, as documented in the [Kubernetes docs](https://kubernetes.io/docs/concepts/security/pod-security-standards/), please set a restricted profile that disables `NET_RAW` on non-trustable pods.
 :::
 
 ### Inbound Rules for K3s Nodes

i18n/zh/docusaurus-plugin-content-docs/current/installation/requirements.md

@@ -18,7 +18,6 @@ K3s is available for the following architectures:
 - x86_64
 - armhf
 - arm64/aarch64
-- s390x
 
 :::warning ARM64 Page Size
 
@@ -127,7 +126,7 @@ The VXLAN port on nodes should not be exposed to the world as it opens up your c
 :::
 
 :::danger
-Flannel relies on the [Bridge CNI plugin](https://www.cni.dev/plugins/current/main/bridge/) to create a L2 network that switches traffic. Rogue pods with `NET_RAW` capabilities can abuse that L2 network to launch attacks such as [ARP spoofing](https://static.sched.com/hosted_files/kccncna19/72/ARP%20DNS%20spoof.pdf). Therefore, as documented in the [Kubernetes docs](https://kubernetes.io/docs/concepts/security/pod-security-standards/), please set a restricted profile that disables `NET_RAW` on non-trustable pods.
+Flannel relies on the [Bridge CNI plugin](https://www.cni.dev/plugins/current/main/bridge/) to create a L2 network that switches traffic. Rogue pods with `NET_RAW` capabilities can abuse that L2 network to launch attacks such as ARP spoofing. Therefore, as documented in the [Kubernetes docs](https://kubernetes.io/docs/concepts/security/pod-security-standards/), please set a restricted profile that disables `NET_RAW` on non-trustable pods.
 :::
 
 ### Inbound Rules for K3s Nodes