Skip to content

elaborating on the new target service and port selection functionality #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 28, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,9 @@ When editing a route:
- Use the `Name` field to set the route name.
- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
- 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
`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.
`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`
value from the drop-down list of available services in the WebLogic Kubernetes Operator domain's namespace. After the `Target Service` is selected,
you can select the `Target Port` from the list of available ports in the selected target service.
- Specify the `Transport Option` for the ingress route:
* Select `Plain HTTP` for unencrypted traffic from the client through the ingress controller to the target service.
* Select `SSL terminate at ingress controller` for SSL
Expand Down