2.0-2.4: Fix validation errors

This commit is contained in:
Billy Tat
2022-08-25 23:41:32 -07:00
parent 331b43a83c
commit 5f390a835b
10 changed files with 237 additions and 225 deletions
@@ -153,6 +153,7 @@ If you're using **Custom: Choose from your existing VPC and Subnets**:
1. Click **Next: Select Subnets**. Then choose one of the **Subnets** that displays.
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.
@@ -109,7 +109,7 @@ Select a pod status that triggers an alert:
- **Not Running**
- **Not Scheduled**
- **Restarted <x> times within the last <x> Minutes**
- **Restarted &lt;x&gt; times within the last &lt;x&gt; Minutes**
### Send a
@@ -123,7 +123,7 @@ Select the urgency level of the alert based on pod state. For example, select **
### Advanced Options
By default, the below options will apply to all alert rules within the group.
By default, the below options will apply to all alert rules within the group.
You can disable these advanced options when configuring a specific rule.
@@ -157,7 +157,7 @@ Select the urgency level of the alert based on the percentage you choose and the
### Advanced Options
By default, the below options will apply to all alert rules within the group.
By default, the below options will apply to all alert rules within the group.
You can disable these advanced options when configuring a specific rule.