Merge remote-tracking branch 'upstream/main' into dev-1.24

content/en/docs/setup/best-practices/enforcing-pod-security-standards.md

@@ -70,6 +70,8 @@ few different ways:
 Other alternatives for enforcing security profiles are being developed in the Kubernetes
 ecosystem:
 
+- [Kubewarden](https://github.com/kubewarden).
+- [Kyverno](https://kyverno.io/policies/).
 - [OPA Gatekeeper](https://github.com/open-policy-agent/gatekeeper).
 
 The decision to go with a _built-in_ solution (e.g. PodSecurity admission controller) versus a

content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md

@@ -225,6 +225,10 @@ sudo systemctl enable --now kubelet
 
   - You can leave SELinux enabled if you know how to configure it but it may require settings that are not supported by kubeadm.
 
+  - If the `baseurl` fails because your Red Hat-based distribution cannot interpret `basearch`, replace `\$basearch` with your computer's architecture.
+  Type `uname -m` to see that value.
+  For example, the `baseurl` URL for `x86_64` could be: `https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64`.
+
 {{% /tab %}}
 {{% tab name="Without a package manager" %}}
 Install CNI plugins (required for most pod network):