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
If an application in a container requires HTTPS, one needs to set the
'proxy_path https://...' instead of 'proxy_pass http://...'. With this
patch one can use the annotation:
'nginx.org/ssl-services: "service1[,service2,...]"'
to specify, which services require HTTPS.
Fixes#61
To load balance an application that requires HTTPS with NGINX Ingress controllers, you need to add the **nginx.org/ssl-services** annotation to your Ingress resource definition. The annotation specifies which services are SSL services. The annotation syntax is as follows:
4
+
```
5
+
nginx.org/ssl-services: "service1[,service2,...]"
6
+
```
7
+
8
+
In the following example we load balance three applications, one of which requires HTTPS:
9
+
```yaml
10
+
apiVersion: extensions/v1beta1
11
+
kind: Ingress
12
+
metadata:
13
+
name: cafe-ingress
14
+
annotations:
15
+
nginx.org/ssl-services: "ssl-svc"
16
+
spec:
17
+
rules:
18
+
- host: cafe.example.com
19
+
http:
20
+
paths:
21
+
- path: /tea
22
+
backend:
23
+
serviceName: tea-svc
24
+
servicePort: 80
25
+
- path: /coffee
26
+
backend:
27
+
serviceName: coffee-svc
28
+
servicePort: 80
29
+
- path: /ssl
30
+
backend:
31
+
serviceName: ssl-svc
32
+
servicePort: 443
33
+
```
34
+
*ssl-svc* is a service for an HTTPS application. The service becomes available at the `/ssl` path. Note how we used the **nginx.org/ssl-services** annotation.
0 commit comments