Merge pull request #557 from btat/forward-port-pr342-pr344

Forward port #342 and #344 to 2.7 docs
This commit is contained in:
Billy Tat
2023-04-25 16:18:32 -07:00
committed by GitHub
3 changed files with 7 additions and 7 deletions
@@ -22,10 +22,10 @@ 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 `/`.
2. Add a **Target Service**.
3. **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.
4. Enter the **Port** number that each target operates on.
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.
## Certificates