public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-29 14:38:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos

Browse Source
This commit is contained in:
Billy Tat
2023-04-24 14:26:06 -07:00
parent d3c5c8d3fa
commit 13e4b8e6f1
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md
+2 -2
View File
@@ -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. 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. 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. 1. Enter the **Port** number that each target operates on.
## Certificates ## Certificates
versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-resources-setup/load-balancer-and-ingress-controller/ingress-configuration.md
+1 -1
View File
@@ -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. 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. 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. 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. **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. 1. Enter the **Port** number that each target operates on.