Building the Ingress Controller Image

Prerequisites

Before you can build the image, make sure that the following software is installed on your machine:

• Docker
• GNU Make
• git
• OpenSSL, optionally, if you would like to generate a self-signed certificate and a key for the default server.
• For NGINX Plus, you must have the NGINX Plus license – the certificate (nginx-repo.crt) and the key (nginx-repo.key).

Although the Ingress controller is written in golang, golang is not required, as the Ingress controller binary will be built in a Docker container.

Building the Image and Pushing It to the Private Registry

We build the image using the make utility and the provided Makefile. Let’s create the controller binary, build an image and push the image to the private registry.

1. Make sure to run the docker login command first to login to the registry. If you’re using Google Container Registry, you don’t need to use the docker command to login – make sure you’re logged into the gcloud tool (using the gcloud auth login command) and set the variable PUSH_TO_GCR=1 when running the make command.

2. Clone the Ingress controller repo:

   $ git clone https://github.com/nginxinc/kubernetes-ingress/
   $ cd kubernetes-ingress
   $ git checkout v1.6.2
   

3. Build the image:

   • For NGINX:

     $ make clean
     $ make PREFIX=myregistry.example.com/nginx-ingress
     

     myregistry.example.com/nginx-ingress defines the repo in your private registry where the image will be pushed. Substitute that value with the repo in your private registry.

     As the result, the image myregistry.example.com/nginx-ingress:1.6.2 is built and pushed to the registry. Note that the tag 1.6.2 comes from the VERSION variable, defined in the Makefile.

   • For NGINX Plus, first, make sure that the certificate (nginx-repo.crt) and the key (nginx-repo.key) of your license are located in the root of the project:

     $ ls nginx-repo.*
     nginx-repo.crt  nginx-repo.key
     

     Then run:

     $ make clean
     $ make DOCKERFILE=DockerfileForPlus PREFIX=myregistry.example.com/nginx-plus-ingress
     

     myregistry.example.com/nginx-plus-ingress defines the repo in your private registry where the image will be pushed. Substitute that value with the repo in your private registry.

     As the result, the image myregistry.example.com/nginx-plus-ingress:1.6.2 is built and pushed to the registry. Note that the tag 1.6.2 comes from the VERSION variable, defined in the Makefile.

Next you will find the details about available Makefile targets and variables.