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

content/en/docs/setup/production-environment/container-runtimes.md

@@ -79,7 +79,7 @@ If systemd doesn't use cgroup v2 by default, you can configure the system to use
 # dnf install -y grubby && \
   sudo grubby \
   --update-kernel=ALL \
-  --args=”systemd.unified_cgroup_hierarchy=1"
+  --args="systemd.unified_cgroup_hierarchy=1"
 ```
 
 To apply the configuration, it is necessary to reboot the node.

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

@@ -383,6 +383,12 @@ Run 'kubectl get nodes' on control-plane to see this machine join.
 A few seconds later, you should notice this node in the output from `kubectl get
 nodes` when run on the control-plane node.
 
+{{< note >}}
+As the cluster nodes are usually initialized sequentially, the CoreDNS Pods are likely to all run 
+on the first control-plane node. To provide higher availability, please rebalance the CoreDNS Pods 
+with `kubectl -n kube-system rollout restart deployment coredns` after at least one new node is joined.
+{{< /note >}}
+
 ### (Optional) Controlling your cluster from machines other than the control-plane node
 
 In order to get a kubectl on some other computer (e.g. laptop) to talk to your

content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md

@@ -76,7 +76,7 @@ then paging can slow down performance.
 You can place bounds on memory use for workloads using the kubelet
 parameters `--kubelet-reserve` and/or `--system-reserve`; these account
 for memory usage on the node (outside of containers), and reduce
-[NodeAllocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable)).
+[NodeAllocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable).
 As you deploy workloads, set resource limits on containers. This also subtracts from
 `NodeAllocatable` and prevents the scheduler from adding more pods once a node is full.