From 13e4b8e6f15e08c83dc815fae2767d331c573593 Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Mon, 24 Apr 2023 14:26:06 -0700 Subject: [PATCH] Fix typos --- .../ingress-configuration.md | 4 ++-- .../ingress-configuration.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md b/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md index 70d4575957c..f2354ec4c59 100644 --- a/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md +++ b/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md @@ -15,9 +15,9 @@ Because of this change to the controller, the default behavior no longer sets `h If you use this option, Ingress routes requests for a hostname to the service or workload that you specify. -1. Specify a path of type `Prefix` and a specify a path such as `/`. +1. Specify a path of type `Prefix` and specify a path such as `/`. 1. Add a **Target Service**. -1. **Optional:** If you want specify a workload or service when a request is sent to a particular hostname path, add a **Path** for the target. For example, if you want requests for `www.mysite.com/contact-us` to be sent to a different service than `www.mysite.com`, enter `/contact-us` in the **Path** field. Typically, the first rule that you create does not include a path. +1. **Optional:** If you want to specify a workload or service when a request is sent to a particular hostname path, add a **Path** for the target. For example, if you want requests for `www.mysite.com/contact-us` to be sent to a different service than `www.mysite.com`, enter `/contact-us` in the **Path** field. Typically, the first rule that you create does not include a path. 1. Enter the **Port** number that each target operates on. ## Certificates diff --git a/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md b/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md index b1c6e3acef6..e80f2a67d1b 100644 --- a/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md +++ b/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md @@ -22,7 +22,7 @@ Because of this change to the controller, the default behavior no longer sets `h If you use this option, Ingress routes requests for a hostname to the service or workload that you specify. 1. Enter the **Request Host** that your Ingress controller will handle request forwarding for. For example, `www.mysite.com`. -1. Specify a path of type `Prefix` and a specify a path such as `/`. +1. Specify a path of type `Prefix` and specify a path such as `/`. 1. Add a **Target Service**. 1. **Optional:** If you want to specify a workload or service when a request is sent to a particular hostname path, add a **Path** for the target. For example, if you want requests for `www.mysite.com/contact-us` to be sent to a different service than `www.mysite.com`, enter `/contact-us` in the **Path** field. The first rule that you create does not typically include a path. 1. Enter the **Port** number that each target operates on.