Skip to content

Commit 1f6c84a

Browse files
committed
update documentation
1 parent 6e05442 commit 1f6c84a

File tree

2 files changed

+16
-8
lines changed

2 files changed

+16
-8
lines changed

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

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,8 @@ cluster attempts to pull the image and start the container.
4949
- The `Docker Registry Secret Name` field specifies the name of the Kubernetes pull secret to use when pulling the image.
5050
To create this secret, enable `Create Docker Hub Secret` and fill in the pull secret data in the `Docker Hub Username`, `Docker Hub Password`,
5151
and `Docker Hub Email Address` fields.
52+
- For NGINX ingress controller, if you desire to have SSL pass through ingress route, enable `
53+
Allow SSL pass through to target service`.
5254

5355
#### TLS Secret for Ingress Routes
5456
Use this pane to configure the Transport Layer Security (TLS) secret containing the certificate and private key data that will be used by the
@@ -86,11 +88,17 @@ When editing a route:
8688
- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
8789
- 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
8890
`Target Service Namespace` field and the port specified by the `Target Port` field.
89-
- To enable TLS between the client
90-
and the ingress controller, enable the `Enable TLS` option. Remember, enabling TLS means that the TLS secret
91-
information must be provided in the `TLS Secret for Ingress Routes` pane. Different ingress controllers support advanced ingress route configuration using ingress controller-specific annotations.
91+
- Specify transport option for the ingress route.
92+
* Select `Plain HTTP` for unencrypted traffic from client through ingress controller to the target service
93+
* Select `SSL terminate at ingress controller` for SSL
94+
terminate
95+
at ingress controller and then unencrypted traffic from ingress controller to target service. Check `Is
96+
target service WebLogic Console?
97+
` if the target service is `WebLogic Console` service.
98+
* Select `SSL pass through` for SSL traffic pass through ingress
99+
controller and terminate at target service. Make sure the `Target Port` is SSL port.
92100
- Use the `Ingress Route Annotations` table to
93-
add annotations to the ingress route, as needed.
101+
add annotations to the ingress route, as needed. Do not remove any pre-populated annotations.
94102

95103
### Code View
96104
The `Code View` displays shell scripts for installing an ingress controller and for updating ingress routes. It also

electron/app/locales/en/webui.json

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -608,7 +608,7 @@
608608
"ingress-design-ingress-namespace-help": "The Kubernetes namespace to use for the ingress controller.",
609609
"ingress-design-voyager-provider-label": "Kubernetes Cluster Provider for Voyager",
610610
"ingress-design-voyager-provider-help": "The Kubernetes cluster provider type to use for Voyager.",
611-
"ingress-design-nginx-allow-passthrough-label": "Allow SSL pass through to backend service",
611+
"ingress-design-nginx-allow-passthrough-label": "Allow SSL pass through to target service",
612612
"ingress-design-nginx-allow-passthrough-help": "Enable this allows creating SSL pass through ingress transport to the target service.",
613613
"ingress-design-specify-docker-registry-secret-label": "Use Docker Hub Secret",
614614
"ingress-design-specify-docker-registry-secret-help": "Whether to use a Docker Hub credential secret to pull the ingress controller image. This is helpful if you encounter a Docker Hub pull limit exceeded error.",
@@ -634,10 +634,10 @@
634634
"ingress-design-ingress-route-tls-label": "Transport Options",
635635
"ingress-design-ingress-route-tls-help": "Select the transport option for this ingress route",
636636
"ingress-design-ingress-route-tlsoption-plain": "Plain HTTP",
637-
"ingress-design-ingress-route-tlsoption-ssl-passthrough": "SSL pass through ingress directly to the target service",
638-
"ingress-design-ingress-route-tlsoption-ssl-terminate-ingress": "SSL terminate at ingress and then plain HTTP traffic from ingress to target service",
637+
"ingress-design-ingress-route-tlsoption-ssl-passthrough": "SSL pass through",
638+
"ingress-design-ingress-route-tlsoption-ssl-terminate-ingress": "SSL terminate at ingress controller",
639639
"ingress-design-ingress-route-is-console-svc-label": "Is target service WebLogic Console?",
640-
"ingress-design-ingress-route-is-console-svc-help": "For SSL terminating at ingress and accessing WebLogic Console Service, turn on this option",
640+
"ingress-design-ingress-route-is-console-svc-help": "For SSL terminating at ingress and accessing WebLogic Console Service, turn on this option. Your domain must have 'WeblogicPluginEnabled: true' in the 'resources->WebAppContainer' section",
641641
"ingress-design-ingress-route-name-label": "Name",
642642
"ingress-design-ingress-route-dialog-title": "Edit Ingress Route",
643643
"ingress-design-ingress-route-annotation-label": "Annotation",

0 commit comments

Comments
 (0)