Merge branch 'rancher:main' into unable-to-attach-mount-volumes-398

docs/getting-started/installation-and-upgrade/installation-requirements/port-requirements.md

@@ -302,36 +302,38 @@ SUSE Linux may have a firewall that blocks all ports by default. To open the por
 
 <Tabs>
 <TabItem value="SLES 15 / openSUSE Leap 15">
+
 1. SSH into the instance.
 1. Start YaST in text mode:
-```
-sudo yast2
-```
+    ```
+    sudo yast2
+    ```
 
 1. Navigate to **Security and Users** > **Firewall** > **Zones:public** > **Ports**. To navigate within the interface, follow the instructions [here](https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha-yast-text.html#sec-yast-cli-navigate).
 1. To open the required ports, enter them into the **TCP Ports** and **UDP Ports** fields. In this example, ports 9796 and 10250 are also opened for monitoring. The resulting fields should look similar to the following:
-```yaml
-TCP Ports
-22, 80, 443, 2376, 2379, 2380, 6443, 9099, 9796, 10250, 10254, 30000-32767
-UDP Ports
-8472, 30000-32767
-```
+    ```yaml
+    TCP Ports
+    22, 80, 443, 2376, 2379, 2380, 6443, 9099, 9796, 10250, 10254, 30000-32767
+    UDP Ports
+    8472, 30000-32767
+    ```
 
 1. When all required ports are enter, select **Accept**.
 
 </TabItem>
 <TabItem value="SLES 12 / openSUSE Leap 42">
+
 1. SSH into the instance.
 1. Edit /`etc/sysconfig/SuSEfirewall2` and open the required ports. In this example, ports 9796 and 10250 are also opened for monitoring:
-  ```
-  FW_SERVICES_EXT_TCP="22 80 443 2376 2379 2380 6443 9099 9796 10250 10254 30000:32767"
-  FW_SERVICES_EXT_UDP="8472 30000:32767"
-  FW_ROUTE=yes
-  ```
+    ```
+    FW_SERVICES_EXT_TCP="22 80 443 2376 2379 2380 6443 9099 9796 10250 10254 30000:32767"
+    FW_SERVICES_EXT_UDP="8472 30000:32767"
+    FW_ROUTE=yes
+    ```
 1. Restart the firewall with the new ports:
-  ```
-  SuSEfirewall2
-  ```
+    ```
+    SuSEfirewall2
+    ```
 
 </TabItem>
 </Tabs>

docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md

@@ -9,7 +9,7 @@ For Kubernetes v1.21 and up, the NGINX Ingress controller no longer runs in host
 
 Because of this change to the controller, the default behavior no longer sets `hostNetwork` to `true`. However, you must set `hostNetwork` to `true` for TCP- and UDP-based Services to work.
 
-:::note
+:::
 
 ## Specify a hostname to use