Skip to content

Commit 417da4f

Browse files
elaborating on the new target service and port selection functionality (#80)
* elaborating on the new target service and port selection functionality * making recommended changes
1 parent db527df commit 417da4f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,9 @@ When editing a route:
8686
- Use the `Name` field to set the route name.
8787
- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
8888
- All requests in the defined rules are routed to the service specified by the `Target Service` field that resides in the namespace specified by the read-only
89-
`Target Service Namespace` field and the port specified by the `Target Port` field. Once the domain has been deployed, you can also select the values from the drop down list.
89+
`Target Service Namespace` field and the port specified by the `Target Port` field. After the domain has been deployed, you can select the `Target Service`
90+
value from the drop-down list of available services in the WebLogic Kubernetes Operator domain's namespace. After the `Target Service` is selected,
91+
you can select the `Target Port` from the list of available ports in the selected target service.
9092
- Specify the `Transport Option` for the ingress route:
9193
* Select `Plain HTTP` for unencrypted traffic from the client through the ingress controller to the target service.
9294
* Select `SSL terminate at ingress controller` for SSL

0 commit comments

Comments
 (0)