From 4c753fc51f3222f5b9eb33ce5c46236462e9ac27 Mon Sep 17 00:00:00 2001
From: Joao Morais <jcmoraisjr@gmail.com>
Date: Wed, 10 May 2017 22:01:45 -0300
Subject: [PATCH] Add configmap on deployment instructions

---
 examples/deployment/haproxy/README.md            | 15 +++++++++++++++
 examples/deployment/haproxy/haproxy-ingress.yaml |  1 +
 2 files changed, 16 insertions(+)

diff --git a/examples/deployment/haproxy/README.md b/examples/deployment/haproxy/README.md
index 7ff1199fb..47e320f46 100644
--- a/examples/deployment/haproxy/README.md
+++ b/examples/deployment/haproxy/README.md
@@ -55,6 +55,21 @@ NAME                                       READY     STATUS    RESTARTS   AGE
 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
 
 Deploy HAProxy Ingress:
diff --git a/examples/deployment/haproxy/haproxy-ingress.yaml b/examples/deployment/haproxy/haproxy-ingress.yaml
index 619b2d9cc..84c661b90 100644
--- a/examples/deployment/haproxy/haproxy-ingress.yaml
+++ b/examples/deployment/haproxy/haproxy-ingress.yaml
@@ -20,6 +20,7 @@ spec:
         args:
         - --default-backend-service=default/ingress-default-backend
         - --default-ssl-certificate=default/tls-secret
+        - --configmap=default/haproxy-ingress
         ports:
         - name: http
           containerPort: 80