Kuberneteskubernetes ingress - proxying to a specific url
2020 · 05 · 13
1 min read
Paper
- When the ingress is exposed externally but the server handling it is not a service inside kubernetes but a separate external server, set proxy_pass like below. (Really, if you get creative, anything nginx supports should work.)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
| kind: Ingress
apiVersion: extensions/v1beta1
metadata:
name: gitlab.test.com
namespace: nginx-ingress
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/proxy-connect-timeout: '3600'
nginx.ingress.kubernetes.io/proxy-read-timeout: '3600'
nginx.ingress.kubernetes.io/proxy-send-timeout: '3600'
nginx.ingress.kubernetes.io/send-timeout: '3600'
nginx.ingress.kubernetes.io/server-snippet: |
location ~ / {
proxy_pass http://10.10.10.101:8084;
}
spec:
rules:
- host: gitlab.test.com
http:
paths:
- path: /
backend:
serviceName: nginx-ingress-default-backend
servicePort: 8080
status:
loadBalancer:
ingress:
- {}
|
- The serviceName above is not a real service, it’s a dummy.
- The annotations are added because of websockets. (Not needed if you don’t use websockets)
1
2
3
4
| nginx.ingress.kubernetes.io/proxy-connect-timeout: '3600'
nginx.ingress.kubernetes.io/proxy-read-timeout: '3600'
nginx.ingress.kubernetes.io/proxy-send-timeout: '3600'
nginx.ingress.kubernetes.io/send-timeout: '3600'
|