2.0-2.4: Fix validation errors

2026-09-25 12:38:05 +00:00 · 2022-08-25 23:41:32 -07:00
parent 331b43a83c
commit 5f390a835b
10 changed files with 237 additions and 225 deletions
@@ -121,7 +121,7 @@ C. Prepare the Docker daemon <br/>
 D. Populate the private registry

 <details>
-  <summary>Collecting and Populating Windows Images into the Private Registry"%}}
+  <summary>Collecting and Populating Windows Images into the Private Registry"%}}</summary>

 ### Prerequisites

@@ -45,7 +45,7 @@ If a pod is not in **Running** state, you can dig into the root cause by running
 kubectl --kubeconfig kube_config_rancher-cluster.yml describe pod POD_NAME -n NAMESPACE
 ```

-#### Pod container logs</h3>
+#### Pod container logs

 ```
 kubectl --kubeconfig kube_config_rancher-cluster.yml logs POD_NAME -n NAMESPACE
@@ -34,7 +34,7 @@ The structure of the addons definition in `rancher-cluster.yml` is wrong. In the
 <ul>
 <li>Is each of the base64 encoded certificate string placed directly after the key, for example: `tls.crt: LS01...`, there should be no newline/space before, in between or after.</li>
 <li>Is the YAML properly formatted, each indentation should be 2 spaces as shown in the template files.</li>
-<li>Verify the integrity of your certificate by running this command `cat MyCertificate | base64 -d` on Linux, `cat MyCertificate | base64 -D` on Mac OS . If any error exists, the command output will tell you.
+<li>Verify the integrity of your certificate by running this command `cat MyCertificate | base64 -d` on Linux, `cat MyCertificate | base64 -D` on Mac OS . If any error exists, the command output will tell you.</li>
 </ul>
 </ul>