From 39144bb9872aa9b77f4cd0ed8e8e3d29f6de1a98 Mon Sep 17 00:00:00 2001
From: Jeroen Schutrup <jschutrup@bol.com>
Date: Wed, 15 May 2019 13:53:21 +0200
Subject: [PATCH] Add documentation on how to build the Docker image for
 end-to-end testing

---
 docs/development.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/docs/development.md b/docs/development.md
index 5c5fd2a7a..43afabb4a 100644
--- a/docs/development.md
+++ b/docs/development.md
@@ -95,6 +95,21 @@ $ export REGISTRY=<your-docker-registry>
 
 To find the registry simply run: `docker system info | grep Registry`
 
+### Building the e2e test image
+
+The e2e test image can also be built through the Makefile.
+
+```console
+$ make e2e-test-image
+```
+
+You can then make this image available on your minikube host by exporting the image and loading it with the minikube docker context:
+
+```console
+$ docker save nginx-ingress-controller:e2e |  (eval $(minikube docker-env) && docker load)
+```
+
+
 ### Nginx Controller
 
 Build a raw server binary
@@ -137,6 +152,8 @@ $ cd $GOPATH/src/k8s.io/ingress-nginx
 $ make e2e-test
 ```
 
+NOTE: if your e2e pod keeps hanging in an ImagePullBackoff, make sure you've made your e2e nginx-ingress-controller image available to minikube as explained in [Building the e2e test image](./Building the e2e test image)
+
 To run unit-tests for lua code locally, run:
 
 ```console