@@ -175,7 +175,7 @@ spec:
175
175
istio : ingressgateway
176
176
servers :
177
177
- hosts :
178
- - ' * '
178
+ - ' yourdomain.dns.com '
179
179
port :
180
180
name : http
181
181
number : 80
@@ -190,7 +190,7 @@ spec:
190
190
gateways :
191
191
- domain1-gateway
192
192
hosts :
193
- - ' * '
193
+ - ' yourdomain.dns.com '
194
194
http :
195
195
- match :
196
196
- uri :
@@ -416,13 +416,13 @@ See Istio [Destination Rule](https://istio.io/latest/docs/reference/config/netwo
416
416
417
417
Ingress gateway provides similar functions to ` Kubernetes Ingress ` but with more advanced functionality.
418
418
419
- For example, to configure an Ingress gateway for SSL termination at the gateway:
419
+ I. For example, to configure an Ingress gateway for SSL termination at the gateway:
420
420
421
421
1 . Create a TLS certificate and secret.
422
422
423
423
``` text
424
424
$ openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /tmp/tls1.key -out /tmp/tls1.crt -subj "/CN=secure-domain.org"
425
- $ kubectl -n weblogic-domain1 create secret tls domain1-tls-cert --key /tmp/tls1.key --cert /tmp/tls1.crt
425
+ $ kubectl -n istio-system create secret tls domain1-tls-cert --key /tmp/tls1.key --cert /tmp/tls1.crt
426
426
```
427
427
428
428
2 . Create the Ingress gateway.
@@ -453,8 +453,36 @@ spec:
453
453
hosts:
454
454
- 'regular-domain.org'
455
455
```
456
+
457
+ If you are accessing the WebLogic Console through a secure gateway with SSL termination at the gateway level, enable
458
+ ` WeblogicPluginEnabled ` in the WebLogic domain and add the appropriate request headers. For example,
459
+
460
+ If you are using WDT, add the ` resources ` section in the model YAML file.
461
+
462
+ ``` text
463
+ resources:
464
+ WebAppContainer:
465
+ WeblogicPluginEnabled: true
466
+ ```
467
+
468
+ If you are using WLST, set the ` WeblogicPluginEnabled ` for each server and cluster
469
+
470
+ ``` text
471
+ set('WeblogicPluginEnabled',true)
472
+ ```
456
473
457
- For example, to configure an Ingress gateway for SSL passthrough:
474
+ Set the request headers in the virtual service: (Use ` kubectl explain virtualservice.spec.http.route.headers ` for help)
475
+
476
+ ``` text
477
+ headers:
478
+ request:
479
+ remove: ['WL-Proxy-Client-IP', 'WL-Proxy-SSL']
480
+ set:
481
+ X-Forwarded-Proto: https
482
+ WL-Proxy-SSL: 'true'
483
+ ```
484
+
485
+ II. For example, to configure an Ingress gateway for SSL passthrough:
458
486
459
487
460
488
``` text
@@ -483,4 +511,29 @@ spec:
483
511
- 'regular-domain.org'
484
512
```
485
513
514
+ The virtual service will then configure to match the ` tls ` rule.
515
+
516
+ ``` text
517
+ apiVersion: networking.istio.io/v1alpha3
518
+ kind: VirtualService
519
+ metadata:
520
+ name: sample-domain1-virtualservice
521
+ namespace: sample-domain1-ns
522
+ spec:
523
+ gateways:
524
+ - sample-domain1-gateway
525
+ hosts:
526
+ - secure-domain.org
527
+ tls:
528
+ - match:
529
+ - port: 443
530
+ sniHosts:
531
+ - secure-domain.org
532
+ route:
533
+ - destination:
534
+ host: sample-domain1-admin-server
535
+ port:
536
+ number: 9002
537
+ ```
538
+
486
539
See Istio [ Ingress] ( https://istio.io/latest/docs/tasks/traffic-management/ingress ) .
0 commit comments