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
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,8 @@ cluster attempts to pull the image and start the container.
49
49
- The `Docker Registry Secret Name` field specifies the name of the Kubernetes pull secret to use when pulling the image.
50
50
To create this secret, enable `Create Docker Hub Secret` and fill in the pull secret data in the `Docker Hub Username`, `Docker Hub Password`,
51
51
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`.
52
54
53
55
#### TLS Secret for Ingress Routes
54
56
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:
86
88
- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
87
89
- 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
88
90
`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.
92
100
- 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.
94
102
95
103
### Code View
96
104
The `Code View` displays shell scripts for installing an ingress controller and for updating ingress routes. It also
"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.",
"ingress-design-ingress-route-tlsoption-ssl-terminate-ingress": "SSL terminate at ingress controller",
639
639
"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",
0 commit comments