Skip to content

Commit 76089ff

Browse files
committed
Cherry-pick branch 'rm/known-limitations-doc' into 'release/4.1'
1 parent 6ee8b17 commit 76089ff

File tree

3 files changed

+75
-1
lines changed

3 files changed

+75
-1
lines changed

documentation/site/content/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ See the [operator prerequisites]({{< relref "/introduction/prerequisites/introdu
3939

4040
#### Recent changes and known issues
4141

42-
See the Release Notes for recent changes to the operator and known issues.
42+
See the [Release Notes](https://github.com/oracle/weblogic-kubernetes-operator/releases) for recent changes to the operator and [Known Limitations]({{< relref "/known-limitations/_index.md" >}}) for the current set of known issues.
4343

4444
#### Operator earlier versions
4545

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
title: "Known limitations"
3+
date: 2019-02-23T08:14:59-05:00
4+
weight: 12
5+
draft: false
6+
---
7+
8+
The following sections describe known limitations for WebLogic Kubernetes Operator. Each issue may contain a workaround or an associated issue number.
9+
10+
#### NGINX SSL passthrough ingress service does not work with Kubernetes headless service
11+
12+
**ISSUE**:
13+
When installing NGINX ingress controller with SSL passthrough enabled `--set "controller.extraArgs.enable-ssl-passthrough=true"`, any ingress rule created subsequently, using SSL passthrough to the individual server service, will fail.
14+
15+
```
16+
$ kubectl -n nginx get services
17+
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
18+
nginx-operator-ingress-nginx-controller-admission ClusterIP 10.43.234.82 <none> 443/TCP 3m3s
19+
nginx-operator-ingress-nginx-controller LoadBalancer 10.43.193.149 192.168.106.2 80:32315/TCP,443:31710/TCP 3m3s
20+
```
21+
22+
For example, after creating the domain, the operator creates a headless Kubernetes service for each server and a headed service for the cluster. The individual service for each server is headless as the `CLUSTER-IP` is `None`; the cluster service is headed as the `CLUSTER-IP` has a valid IP address.
23+
24+
```
25+
$ kubectl -n sample-domain1-ns get services
26+
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
27+
sample-domain1-admin-server ClusterIP None <none> 7001/TCP,7002/TCP 23h
28+
sample-domain1-cluster-cluster-1 ClusterIP 10.43.108.163 <none> 8001/TCP,7002/TCP 23h
29+
sample-domain1-managed-server1 ClusterIP None <none> 8001/TCP,7002/TCP 23h
30+
```
31+
32+
If you create a passthrough ingress rule to use SSL passthrough to access the admin server, for example:
33+
34+
```
35+
apiVersion: networking.k8s.io/v1
36+
kind: Ingress
37+
metadata:
38+
name: console-ssl-passthru
39+
namespace: sample-domain1-ns
40+
annotations:
41+
nginx.ingress.kubernetes.io/ssl-passthrough: 'true'
42+
spec:
43+
ingressClassName: nginx
44+
rules:
45+
- http:
46+
paths:
47+
- backend:
48+
service:
49+
name: sample-domain1-admin-server
50+
port:
51+
number: 7002
52+
path: /
53+
pathType: Prefix
54+
host: localk8s.com
55+
```
56+
57+
Accessing the WebLogic Console on the admin server, through the ingress controller, will result in an error.
58+
59+
```
60+
curl -k -v -L https://localk8s.com:31710/console
61+
* Trying 192.168.106.2:31710...
62+
* Connected to localk8s.com (192.168.106.2) port 31710 (#0)
63+
* ALPN: offers h2,http/1.1
64+
* (304) (OUT), TLS handshake, Client hello (1):
65+
* LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localk8s.com:31710
66+
* Closing connection 0
67+
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localk8s.com:31710
68+
```
69+
70+
This is currently reported as an NGINX bug in https://github.com/kubernetes/ingress-nginx/issues/1718

documentation/site/content/managing-domains/accessing-the-domain/ingress/_index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,3 +74,7 @@ Information about how to install and configure these ingress controllers to load
7474
{{% /notice %}}
7575

7676
Samples are also provided for the Traefik ingress controller, showing how to manage multiple WebLogic clusters as the backends, using different routing rules, host-routing and path-routing; and TLS termination: [Traefik samples](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/charts/traefik/samples).
77+
78+
{{% notice info %}}
79+
**NOTE** the following [Known Limitation]({{< relref "/known-limitations#nginx-ssl-passthrough-ingress-service-does-not-work-with-kubernetes-headless-service" >}}), NGINX SSL passthrough ingress service does not work with Kubernetes headless service.
80+
{{% /notice %}}

0 commit comments

Comments
 (0)