You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,9 @@ When editing a route:
86
86
- Use the `Name` field to set the route name.
87
87
- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
88
88
- 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.
90
92
- Specify the `Transport Option` for the ingress route:
91
93
* Select `Plain HTTP` for unencrypted traffic from the client through the ingress controller to the target service.
92
94
* Select `SSL terminate at ingress controller` for SSL
0 commit comments