Release 1.5.1

Author: pleshakov

CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+### 1.5.1
+
+CHANGES:
+* Update NGINX version to 1.17.1.
+
+HELM CHART:
+* The version of the Helm chart is now 0.3.1.
+* [593](https://github.com/nginxinc/kubernetes-ingress/pull/593): Fix the selector in the Ingress Controller service when the `controller.name` parameter is set. This introduces a change, see the HELM UPGRADE section.
+
+UPGRADE:
+* For NGINX, use the 1.5.1 image from our DockerHub: `nginx/nginx-ingress:1.5.1` or `nginx/nginx-ingress:1.5.1-alpine`
+* For NGINX Plus, please build your own image using the 1.5.1 source code.
+* For Helm, use version 0.3.1 of the chart.
+
+HELM UPGRADE:
+
+In the changelog of Release 1.5.0, we advised not to upgrade the helm chart from `0.2.1` to `0.3.0` unless the mentioned in the changelog problems were acceptable. This release we provide mitigation instructions on how to upgrade from `0.2.1` to `0.3.1` without disruptions. 
+
+When you upgrade from `0.2.1` to `0.3.1`, make sure to configure the following parameters:
+* `controller.name` is set to `nginx-ingress` or the previously used value in case you customized it. This ensures the Deployment/Daemonset will not be recreated.
+* `controller.service.name` is set to `nginx-ingress`. This ensures the service will not be recreated.
+* `controller.config.name` is set to `nginx-config`. This ensures the ConfigMap will not be recreated.
+
+Upgrading from `0.3.0` to `0.3.1`: Upgrading is not affected unless you customized `controller.name`. In that case, because of the fix [593](https://github.com/nginxinc/kubernetes-ingress/pull/593), the upgraded service will have a new selector, and the upgraded pod spec will have a new label. As a result, during an upgrade, the old pods will be immediately excluded from the service. Also, for the Deployment, the old pods will not terminate but continue to run. To terminate the old pods, manually remove the corresponding ReplicaSet.
+
 ### 1.5.0
 
 FEATURES:

Makefile

@@ -1,6 +1,6 @@
 all: push
 
-VERSION = 1.5.0
+VERSION = 1.5.1
 TAG = $(VERSION)
 PREFIX = nginx/nginx-ingress
 

README.md

@@ -49,7 +49,7 @@ Read [this doc](docs/nginx-plus.md) to learn more about NGINX Ingress controller
 
 We publish Ingress controller releases on GitHub. See our [releases page](https://github.com/nginxinc/kubernetes-ingress/releases).
 
-The latest stable release is [1.5.0](https://github.com/nginxinc/kubernetes-ingress/releases/tag/v1.5.0). For production use, we recommend that you choose the latest stable release.  As an alternative, you can choose the *edge* version built from the [latest commit](https://github.com/nginxinc/kubernetes-ingress/commits/master) from the master branch. The edge version is useful for experimenting with new features that are not yet published in a stable release.
+The latest stable release is [1.5.1](https://github.com/nginxinc/kubernetes-ingress/releases/tag/v1.5.1). For production use, we recommend that you choose the latest stable release.  As an alternative, you can choose the *edge* version built from the [latest commit](https://github.com/nginxinc/kubernetes-ingress/commits/master) from the master branch. The edge version is useful for experimenting with new features that are not yet published in a stable release.
 
 To use the Ingress controller, you need to have access to:
 * An Ingress controller image.
@@ -62,7 +62,7 @@ The table below summarizes the options regarding the images, manifests, helm cha
 
 | Version | Description |  Image for NGINX | Image for NGINX Plus | Installation Manifests and Helm Chart | Documentation and Examples |
 | ------- | ----------- | --------------- | -------------------- | ---------------------------------------| -------------------------- |
-| Latest stable release | For production use | `nginx/nginx-ingress:1.5.0`, `nginx/nginx-ingress:1.5.0-alpine` from [DockerHub](https://hub.docker.com/r/nginx/nginx-ingress/) or [build your own image](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.0/build). | [Build your own image](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.0/build). | [Manifests](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.0/deployments). [Helm chart](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.0/deployments/helm-chart). | [Documentation](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.0/docs). [Examples](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.0/examples). |
+| Latest stable release | For production use | `nginx/nginx-ingress:1.5.1`, `nginx/nginx-ingress:1.5.1-alpine` from [DockerHub](https://hub.docker.com/r/nginx/nginx-ingress/) or [build your own image](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.1/build). | [Build your own image](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.1/build). | [Manifests](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.1/deployments). [Helm chart](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.1/deployments/helm-chart). | [Documentation](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.1/docs). [Examples](https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.1/examples). |
 | Edge | For testing and experimenting | `nginx/nginx-ingress:edge`, `nginx/nginx-ingress:edge-alpine` from [DockerHub](https://hub.docker.com/r/nginx/nginx-ingress/) or [build your own image](https://github.com/nginxinc/kubernetes-ingress/tree/master/build). | [Build your own image](https://github.com/nginxinc/kubernetes-ingress/tree/master/build). | [Manifests](https://github.com/nginxinc/kubernetes-ingress/tree/master/deployments). [Helm chart](https://github.com/nginxinc/kubernetes-ingress/tree/master/deployments/helm-chart). | [Documentation](https://github.com/nginxinc/kubernetes-ingress/tree/master/docs). [Examples](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples). |
 
 ## Contacts

build/README.md

@@ -30,7 +30,7 @@ We build the image using the make utility and the provided `Makefile`. Let’s c
 1. Clone the Ingress controller repo:
     ```
     $ git clone https://github.com/nginxinc/kubernetes-ingress/
-    $ git checkout v1.5.0
+    $ git checkout v1.5.1
     ```
 
 1. Build the image:
@@ -41,7 +41,7 @@ We build the image using the make utility and the provided `Makefile`. Let’s c
       ```
       `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.5.0** is built and pushed to the registry. Note that the tag `1.5.0` comes from the `VERSION` variable, defined in the Makefile.
+      As the result, the image **myregistry.example.com/nginx-ingress:1.5.1** is built and pushed to the registry. Note that the tag `1.5.1` 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:
       ```
@@ -55,7 +55,7 @@ We build the image using the make utility and the provided `Makefile`. Let’s c
       ```
       `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.5.0** is built and pushed to the registry. Note that the tag `1.5.0` comes from the `VERSION` variable, defined in the Makefile.
+      As the result, the image **myregistry.example.com/nginx-plus-ingress:1.5.1** is built and pushed to the registry. Note that the tag `1.5.1` comes from the `VERSION` variable, defined in the Makefile.
 
 Next you will find the details about available Makefile targets and variables.
 

deployments/daemon-set/nginx-ingress.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       serviceAccountName: nginx-ingress
       containers:
-      - image: nginx/nginx-ingress:1.5.0
+      - image: nginx/nginx-ingress:1.5.1
         name: nginx-ingress
         ports:
         - name: http

deployments/daemon-set/nginx-plus-ingress.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       serviceAccountName: nginx-ingress
       containers:
-      - image: nginx-plus-ingress:1.5.0
+      - image: nginx-plus-ingress:1.5.1
         name: nginx-plus-ingress
         ports:
         - name: http

deployments/deployment/nginx-ingress.yaml

@@ -18,7 +18,7 @@ spec:
     spec:
       serviceAccountName: nginx-ingress
       containers:
-      - image: nginx/nginx-ingress:1.5.0
+      - image: nginx/nginx-ingress:1.5.1
         name: nginx-ingress
         ports:
         - name: http

deployments/deployment/nginx-plus-ingress.yaml

@@ -18,7 +18,7 @@ spec:
     spec:
       serviceAccountName: nginx-ingress
       containers:
-      - image: nginx-plus-ingress:1.5.0
+      - image: nginx-plus-ingress:1.5.1
         name: nginx-plus-ingress
         ports:
         - name: http

deployments/helm-chart/Chart.yaml

@@ -1,10 +1,10 @@
 name: nginx-ingress
-version: 0.3.0 
-appVersion: 1.5.0
+version: 0.3.1 
+appVersion: 1.5.1
 description: NGINX Ingress Controller
-icon: https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/v1.5.0/deployments/helm-chart/chart-icon.png
+icon: https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/v1.5.1/deployments/helm-chart/chart-icon.png
 sources:
-  - https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.0/deployments/helm-chart
+  - https://github.com/nginxinc/kubernetes-ingress/tree/v1.5.1/deployments/helm-chart
 keywords:
   - ingress
   - nginx

deployments/helm-chart/README.md

@@ -9,7 +9,7 @@ This chart deploys the NGINX Ingress controller in your Kubernetes cluster.
   - Helm 2.8.x+.
   - Git (for installation using the chart source files).
   - If you’d like to use NGINX Plus:
-    - Build an Ingress controller image with NGINX Plus and push it to your private registry by following the instructions from [here](https://github.com/nginxinc/kubernetes-ingress/blob/v1.5.0/build/README.md).
+    - Build an Ingress controller image with NGINX Plus and push it to your private registry by following the instructions from [here](https://github.com/nginxinc/kubernetes-ingress/blob/v1.5.1/build/README.md).
     - Configure `controller.nginxplus` and `controller.image.repository` parameters accordingly using a values file or the `--set` flag of the `helm install` command.
 
 ## Installing the Chart
@@ -39,7 +39,7 @@ This chart deploys the NGINX Ingress controller in your Kubernetes cluster.
 1. Clone the Ingress controller repo and check out the latest stable version:
     ```
     $ git clone https://github.com/nginxinc/kubernetes-ingress/
-    $ git checkout v1.5.0
+    $ git checkout v1.5.1
     ```
 2. Change your working directory to /deployments/helm-chart:
     ```
@@ -86,7 +86,7 @@ Parameter | Description | Default
 `controller.hostNetwork` | Enables the Ingress controller pods to use the host's network namespace. | false
 `controller.nginxDebug` | Enables debugging for NGINX. Uses the `nginx-debug` binary. Requires `error-log-level: debug` in the ConfigMap via `controller.config.entries`. | false
 `controller.image.repository` | The image repository of the Ingress controller. | nginx/nginx-ingress
-`controller.image.tag` | The tag of the Ingress controller image. | 1.5.0
+`controller.image.tag` | The tag of the Ingress controller image. | 1.5.1
 `controller.image.pullPolicy` | The pull policy for the Ingress controller image. | IfNotPresent
 `controller.config.name` | The name of the ConfigMap used by the Ingress controller. | Autogenerated
 `controller.config.entries` | The entries of the ConfigMap for customizing NGINX configuration. | {}