From 357a94c5897c947edaec18f4be079d7faf7259d7 Mon Sep 17 00:00:00 2001 From: Robert Patrick Date: Fri, 28 Jan 2022 09:56:24 -0600 Subject: [PATCH 1/2] elaborating on the new target service and port selection functionality --- .../content/navigate/kubernetes/k8s-ingress-controller.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md b/documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md index bdf8ec196..ae82f3d52 100644 --- a/documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md +++ b/documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md @@ -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. Once the domain has been deployed, you can select the `Target Service` + value from the drop-down list of available service in the WebLogic Kubernetes Operator domain's namespace. Once 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 From b3c4d443ea608d039b47d7cf4f8adbc984639c71 Mon Sep 17 00:00:00 2001 From: Robert Patrick Date: Fri, 28 Jan 2022 10:28:52 -0600 Subject: [PATCH 2/2] making recommended changes --- .../content/navigate/kubernetes/k8s-ingress-controller.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md b/documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md index ae82f3d52..9c091a13e 100644 --- a/documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md +++ b/documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md @@ -86,8 +86,8 @@ 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 select the `Target Service` - value from the drop-down list of available service in the WebLogic Kubernetes Operator domain's namespace. Once the `Target Service` is selected, +`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.