Validation errors

2026-09-28 22:18:52 +00:00 · 2022-08-18 11:44:43 -07:00
parent ed61e7808b
commit 1cc972d397
7 changed files with 24 additions and 24 deletions
@@ -73,7 +73,7 @@ The table below details the parameters for the user schema configuration.
 The table below details the parameters for the group schema configuration.
-<figcaption>Group Schema Configuration Parameters<figcaption>
+<figcaption>Group Schema Configuration Parameters</figcaption>
 | Parameter | Description |
 |:--|:--|
@@ -205,7 +205,7 @@ For HPA to work correctly, service deployments should have resources request def
 1. Generate a load for the service to test that your pods autoscale as intended. You can use any load-testing tool (Hey, Gatling, etc.), but we're using [Hey](https://github.com/rakyll/hey).
 1. Test that pod autoscaling works as intended.<br/><br/>
-  **To Test Autoscaling Using Resource Metrics:**
+    **To Test Autoscaling Using Resource Metrics:**
   <details id="observe-upscale-2-pods-cpu">
     <summary>Upscale to 2 Pods: CPU Usage Up to Target</summary>
@@ -58,7 +58,7 @@ Some cloud-managed layer-7 load balancers (such as the ALB ingress controller on
 Other layer-7 load balancers, such as the Google Load Balancer or Nginx Ingress Controller, directly expose one or more IP addresses. Google Load Balancer provides a single routable IP address. Nginx Ingress Controller exposes the external IP of all nodes that run the Nginx Ingress Controller. You can do either of the following:
 1.	Configure your own DNS to map (via A records) your domain name to the IP addresses exposes by the Layer-7 load balancer.
-2.	Ask Rancher to generate an sslip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say a.b.c.d, and generate a host name <ingressname>.<namespace>.a.b.c.d.sslip.io.
+2.	Ask Rancher to generate an sslip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say a.b.c.d, and generate a host name `<ingressname>.<namespace>.a.b.c.d.sslip.io`.
 The benefit of using sslip.io is that you obtain a working entrypoint URL immediately after you create the ingress rule. Setting up your own domain name, on the other hand, requires you to configure DNS servers and wait for DNS to propagate.
@@ -75,7 +75,7 @@ The table below details the parameters for the user schema configuration.
 The table below details the parameters for the group schema configuration.
-<figcaption>Group Schema Configuration Parameters<figcaption>
+<figcaption>Group Schema Configuration Parameters</figcaption>
 | Parameter | Description |
 |:--|:--|
@@ -344,17 +344,17 @@ If you choose to assign a public IP address to your cluster's worker nodes, you
 <details id="yes">
  <summary>Click to expand</summary>
-If you're using **Custom: Choose from your existing VPC and Subnets**:
+    If you're using **Custom: Choose from your existing VPC and Subnets**:
-(If you're using **Standard**, skip to the [instance options.)](#select-instance-options-2-4)
+    (If you're using **Standard**, skip to the [instance options.)](#select-instance-options-2-4)
-1. Make sure **Custom: Choose from your existing VPC and Subnets** is selected.
+    1. Make sure **Custom: Choose from your existing VPC and Subnets** is selected.
-1. From the drop-down that displays, choose a VPC.
+    1. From the drop-down that displays, choose a VPC.
-1. Click **Next: Select Subnets**. Then choose one of the **Subnets** that displays.
+    1. Click **Next: Select Subnets**. Then choose one of the **Subnets** that displays.
-1. Click **Next: Select Security Group**.
+    1. Click **Next: Select Security Group**.
 </details>
 If your worker nodes have Private IPs only, you must also choose a **VPC & Subnet** that allow your instances to access the internet. This access is required so that your worker nodes can connect to the Kubernetes control plane.
@@ -6,7 +6,7 @@ aliases:
  - /rancher/v2.x/en/k8s-in-rancher/horitzontal-pod-autoscaler/testing-hpa/
 ---
-This document describes how to check the status of your HPAs after scaling them up or down with your load testing tool. For information on how to check the status from the Rancher UI (at least version 2.3.x), refer to [Managing HPAs with the Rancher UI]({{<baseurl>}}/rancher/v2.5/en/k8s-in-rancher/horitzontal-pod-autoscaler/manage-hpa-with-kubectl/).
+This document describes how to check the status of your HPAs after scaling them up or down with your load testing tool. For information on how to check the status from the Rancher UI (at least version 2.3.x), refer to [Managing HPAs with the Rancher UI](manage-hpas-with-kubectl.md).
 For HPA to work correctly, service deployments should have resources request definitions for containers. Follow this hello-world example to test if HPA is working correctly.
@@ -67,7 +67,7 @@ For HPA to work correctly, service deployments should have resources request def
         app: hello-world
     ```
-</details>
+   </details>
 1. Deploy it to your cluster.
@@ -205,7 +205,7 @@ For HPA to work correctly, service deployments should have resources request def
 1. Generate a load for the service to test that your pods autoscale as intended. You can use any load-testing tool (Hey, Gatling, etc.), but we're using [Hey](https://github.com/rakyll/hey).
 1. Test that pod autoscaling works as intended.<br/><br/>
-  **To Test Autoscaling Using Resource Metrics:**
+   **To Test Autoscaling Using Resource Metrics:**
   <details id="observe-upscale-2-pods-cpu">
     <summary>Upscale to 2 Pods: CPU Usage Up to Target</summary>
@@ -59,7 +59,7 @@ Some cloud-managed layer-7 load balancers (such as the ALB ingress controller on
 Other layer-7 load balancers, such as the Google Load Balancer or Nginx Ingress Controller, directly expose one or more IP addresses. Google Load Balancer provides a single routable IP address. Nginx Ingress Controller exposes the external IP of all nodes that run the Nginx Ingress Controller. You can do either of the following:
 1.	Configure your own DNS to map (via A records) your domain name to the IP addresses exposes by the Layer-7 load balancer.
-2.	Ask Rancher to generate an sslip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say a.b.c.d, and generate a host name <ingressname>.<namespace>.a.b.c.d.sslip.io.
+2.	Ask Rancher to generate an sslip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say a.b.c.d, and generate a host name `<ingressname>.<namespace>.a.b.c.d.sslip.io`.
 The benefit of using sslip.io is that you obtain a working entrypoint URL immediately after you create the ingress rule. Setting up your own domain name, on the other hand, requires you to configure DNS servers and wait for DNS to propagate.