Add configmap on deployment instructions
This commit is contained in:
parent
f1a0119b22
commit
4c753fc51f
2 changed files with 16 additions and 0 deletions
|
@ -55,6 +55,21 @@ NAME READY STATUS RESTARTS AGE
|
||||||
ingress-default-backend-1110790216-gqr61 1/1 Running 0 10s
|
ingress-default-backend-1110790216-gqr61 1/1 Running 0 10s
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Configmap
|
||||||
|
|
||||||
|
Create a configmap named `haproxy-ingress`:
|
||||||
|
|
||||||
|
```console
|
||||||
|
$ kubectl create configmap haproxy-ingress
|
||||||
|
configmap "haproxy-ingress" created
|
||||||
|
```
|
||||||
|
|
||||||
|
A configmap is used to provide global or default configuration like
|
||||||
|
timeouts, SSL/TLS settings, a syslog service endpoint and so on. The
|
||||||
|
configmap can be edited or replaced later in order to apply new
|
||||||
|
configuration on a running ingress controller. All supported options
|
||||||
|
are [here](https://github.com/jcmoraisjr/haproxy-ingress#configmap).
|
||||||
|
|
||||||
## Controller
|
## Controller
|
||||||
|
|
||||||
Deploy HAProxy Ingress:
|
Deploy HAProxy Ingress:
|
||||||
|
|
|
@ -20,6 +20,7 @@ spec:
|
||||||
args:
|
args:
|
||||||
- --default-backend-service=default/ingress-default-backend
|
- --default-backend-service=default/ingress-default-backend
|
||||||
- --default-ssl-certificate=default/tls-secret
|
- --default-ssl-certificate=default/tls-secret
|
||||||
|
- --configmap=default/haproxy-ingress
|
||||||
ports:
|
ports:
|
||||||
- name: http
|
- name: http
|
||||||
containerPort: 80
|
containerPort: 80
|
||||||
|
|
Loading…
Reference in a new issue