You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+25-12Lines changed: 25 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,18 @@
1
1
# Changelog
2
2
3
+
### 1.6.2
4
+
5
+
CHANGES:
6
+
* Update NGINX version to 1.17.8.
7
+
8
+
HELM CHART:
9
+
* The version of the Helm chart is now 0.4.2.
10
+
11
+
UPGRADE:
12
+
* For NGINX, use the 1.6.2 image from our DockerHub: `nginx/nginx-ingress:1.6.2` or `nginx/nginx-ingress:1.6.2-alpine`
13
+
* For NGINX Plus, please build your own image using the 1.6.2 source code.
14
+
* For Helm, use version 0.4.2 of the chart.
15
+
3
16
### 1.6.1
4
17
5
18
CHANGES:
@@ -17,7 +30,7 @@ UPGRADE:
17
30
18
31
OVERVIEW:
19
32
20
-
Release 1.6.0 includes:
33
+
Release 1.6.0 includes:
21
34
* Improvements to VirtualServer and VirtualServerRoute resources, adding support for richer load balancing behavior, more sophisticated request routing, redirects, direct responses, and blue-green and circuit breaker patterns. The VirtualServer and VirtualServerRoute resources are enabled by default and are ready for production use.
22
35
* Support for OpenTracing, helping you to monitor and debug complex transactions.
23
36
* An improved security posture, with support to run the Ingress Controller as a non-root user.
@@ -54,7 +67,7 @@ FEATURES FOR VIRTUALSERVER AND VIRTUALSERVERROUTE RESOURCES:
54
67
*[596](https://github.com/nginxinc/kubernetes-ingress/pull/596): Add lb-method support in vs and vsr.
55
68
56
69
FEATURES:
57
-
*[750](https://github.com/nginxinc/kubernetes-ingress/pull/750): Add support for health status uri customisation.
70
+
*[750](https://github.com/nginxinc/kubernetes-ingress/pull/750): Add support for health status uri customisation.
58
71
*[691](https://github.com/nginxinc/kubernetes-ingress/pull/691): Helper Functions for custom annotations.
59
72
*[631](https://github.com/nginxinc/kubernetes-ingress/pull/631): Add max_conns support for NGINX plus.
60
73
*[629](https://github.com/nginxinc/kubernetes-ingress/pull/629): Added upstream zone directive annotation. Thanks to [Victor Regalado](https://github.com/vrrs).
@@ -212,7 +225,7 @@ UPGRADE:
212
225
213
226
HELM UPGRADE:
214
227
215
-
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.
228
+
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.
216
229
217
230
When you upgrade from `0.2.1` to `0.3.1`, make sure to configure the following parameters:
218
231
*`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.
@@ -240,9 +253,9 @@ BUGFIXES:
240
253
241
254
HELM CHART:
242
255
* The version of the helm chart is now 0.3.0.
243
-
* The helm chart is now available in our helm chart repo `helm.nginx.com/stable`.
256
+
* The helm chart is now available in our helm chart repo `helm.nginx.com/stable`.
244
257
* Add new parameters to the Chart: `controller.service.httpPort.targetPort`, `controller.service.httpsPort.targetPort`, `controller.service.name`, `controller.pod.annotations`, `controller.config.name`, `controller.reportIngressStatus.leaderElectionLockName`, `controller.service.httpPort`, `controller.service.httpsPort`, `controller.service.loadBalancerIP`, `controller.service.loadBalancerSourceRanges`, `controller.tolerations`, `controller.affinity`. Added in [562](https://github.com/nginxinc/kubernetes-ingress/pull/562), [561](https://github.com/nginxinc/kubernetes-ingress/pull/561), [553](https://github.com/nginxinc/kubernetes-ingress/pull/553), [534](https://github.com/nginxinc/kubernetes-ingress/pull/534) thanks to [Paulo Ribeiro](https://github.com/paigr), [479](https://github.com/nginxinc/kubernetes-ingress/pull/479) thanks to [Alejandro Llanes](https://github.com/sombralibre), [468](https://github.com/nginxinc/kubernetes-ingress/pull/468), [456](https://github.com/nginxinc/kubernetes-ingress/pull/456).
245
-
*[546](https://github.com/nginxinc/kubernetes-ingress/pull/546): Support deploying multiple Ingress Controllers in a cluster. **Note**: The generated resources have new names that are unique for each Ingress Controller. As a consequence, the name change affects the upgrade. See the HELM UPGRADE section for more information.
258
+
*[546](https://github.com/nginxinc/kubernetes-ingress/pull/546): Support deploying multiple Ingress Controllers in a cluster. **Note**: The generated resources have new names that are unique for each Ingress Controller. As a consequence, the name change affects the upgrade. See the HELM UPGRADE section for more information.
246
259
*[542](https://github.com/nginxinc/kubernetes-ingress/pull/542): Reduce the required privileges in the RBAC manifests.
247
260
248
261
CHANGES:
@@ -257,8 +270,8 @@ UPGRADE:
257
270
HELM UPGRADE:
258
271
259
272
The new version of the helm chart uses different names for the generated resources. This makes it possible to deploy multiple Ingress Controllers in a cluster. However, as a side effect, during the upgrade from the previous version, helm will recreate the resources, instead of updating the existing ones. This, in turn, might cause problems for the following resources:
260
-
* Service: If the service was created with the type LoadBalancer, the public IP of the new service might change. Additionally, helm updates the selector of the service, so that the old pods will be immediately excluded from the service.
261
-
* Deployment/DaemonSet: Because the resource is recreated, the old pods will be removed and the new ones will be launched, instead of the default Deployment/Daemonset upgrade strategy.
273
+
* Service: If the service was created with the type LoadBalancer, the public IP of the new service might change. Additionally, helm updates the selector of the service, so that the old pods will be immediately excluded from the service.
274
+
* Deployment/DaemonSet: Because the resource is recreated, the old pods will be removed and the new ones will be launched, instead of the default Deployment/Daemonset upgrade strategy.
262
275
* ConfigMap: After the helm removes the resource, the old Ingress Controller pods will be immediately reconfigured to use the default values of the ConfigMap keys. During a small window between the reconfiguration and the shutdown of the old pods, NGINX will use the configuration with the default values.
263
276
264
277
We advise not to upgrade to the new version of the helm chart unless the mentioned problems are acceptable for your case. We will provide special upgrade instructions for helm that mitigate the problems for the next minor release of the Ingress Controller (1.5.1).
@@ -366,7 +379,7 @@ HELM CHART:
366
379
* The version of the Helm chart is now 0.2.0.
367
380
368
381
CHANGES:
369
-
* Update NGINX version to 1.15.6.
382
+
* Update NGINX version to 1.15.6.
370
383
* Update NGINX Plus version to R16p1.
371
384
* Update NGINX Prometheus Exporter to 0.2.0.
372
385
*[430](https://github.com/nginxinc/kubernetes-ingress/pull/430): Add the `controller.serviceAccount.imagePullSecrets` parameter to the helm chart. **Note**: the `controller.serviceAccountName` parameter has been changed to `controller.serviceAccount.name`.
*[258](https://github.com/nginxinc/kubernetes-ingress/pull/258): Handle annotations and conflicting paths for MergeableTypes. Thanks to [Fernando Diaz](https://github.com/diazjf).
*[249](https://github.com/nginxinc/kubernetes-ingress/pull/249): Add support for prometheus for Plus.
446
459
*[241](https://github.com/nginxinc/kubernetes-ingress/pull/241): Update the doc about building the Docker image.
447
460
*[240](https://github.com/nginxinc/kubernetes-ingress/pull/240): Use new NGINX Plus API.
@@ -484,7 +497,7 @@ UPGRADE:
484
497
485
498
*[175](https://github.com/nginxinc/kubernetes-ingress/pull/175): Add support for JWT for NGINX Plus.
486
499
*[171](https://github.com/nginxinc/kubernetes-ingress/pull/171): Allow NGINX to listen on non-standard ports. Thanks to [Stanislav Seletskiy](https://github.com/seletskiy).
487
-
*[170](https://github.com/nginxinc/kubernetes-ingress/pull/170): Add the default server. **Note**: The Ingress controller will fail to start if there are no cert and key for the default server. You can pass a TLS Secret for the default server as an argument to the Ingress controller or add a cert and a key to the Docker image.
500
+
*[170](https://github.com/nginxinc/kubernetes-ingress/pull/170): Add the default server. **Note**: The Ingress controller will fail to start if there are no cert and key for the default server. You can pass a TLS Secret for the default server as an argument to the Ingress controller or add a cert and a key to the Docker image.
488
501
*[169](https://github.com/nginxinc/kubernetes-ingress/pull/169): Ignore Ingress resources with empty hostnames.
489
502
*[168](https://github.com/nginxinc/kubernetes-ingress/pull/168): Add the `nginx.org/lb-method` annotation. Thanks to [Sajal Kayan](https://github.com/sajal).
490
503
*[166](https://github.com/nginxinc/kubernetes-ingress/pull/166): Watch Secret resources for updates. **Note**: If a Secret referenced by one or more Ingress resources becomes invalid or gets removed, the configuration for those Ingress resources will be disabled until there is a valid Secret.
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ Read [this doc](docs/nginx-plus.md) to learn more about NGINX Ingress controller
49
49
50
50
We publish Ingress controller releases on GitHub. See our [releases page](https://github.com/nginxinc/kubernetes-ingress/releases).
51
51
52
-
The latest stable release is [1.6.1](https://github.com/nginxinc/kubernetes-ingress/releases/tag/v1.6.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.
52
+
The latest stable release is [1.6.2](https://github.com/nginxinc/kubernetes-ingress/releases/tag/v1.6.2). 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.
53
53
54
54
To use the Ingress controller, you need to have access to:
55
55
* An Ingress controller image.
@@ -62,7 +62,7 @@ The table below summarizes the options regarding the images, manifests, helm cha
62
62
63
63
| 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.6.1`, `nginx/nginx-ingress:1.6.1-alpine` from [DockerHub](https://hub.docker.com/r/nginx/nginx-ingress/) or [build your own image](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/). |[Build your own image](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/). |[Manifests](https://github.com/nginxinc/kubernetes-ingress/tree/v1.6.1/deployments). [Helm chart](https://github.com/nginxinc/kubernetes-ingress/tree/v1.6.1/deployments/helm-chart). |[Documentation](https://docs.nginx.com/nginx-ingress-controller/). [Examples](https://docs.nginx.com/nginx-ingress-controller/configuration/configuration-examples/). |
65
+
| Latest stable release | For production use |`nginx/nginx-ingress:1.6.2`, `nginx/nginx-ingress:1.6.2-alpine` from [DockerHub](https://hub.docker.com/r/nginx/nginx-ingress/) or [build your own image](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/). |[Build your own image](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/). |[Manifests](https://github.com/nginxinc/kubernetes-ingress/tree/v1.6.2/deployments). [Helm chart](https://github.com/nginxinc/kubernetes-ingress/tree/v1.6.2/deployments/helm-chart). |[Documentation](https://docs.nginx.com/nginx-ingress-controller/). [Examples](https://docs.nginx.com/nginx-ingress-controller/configuration/configuration-examples/). |
66
66
| 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/docs-web/installation/building-ingress-controller-image.md). |[Build your own image](https://github.com/nginxinc/kubernetes-ingress/tree/master/docs-web/installation/building-ingress-controller-image.md). |[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-web). [Examples](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples). |
`controller.nginxDebug` | Enables debugging for NGINX. Uses the `nginx-debug` binary. Requires `error-log-level: debug` in the ConfigMap via `controller.config.entries`. | false
124
124
`controller.logLevel` | The log level of the Ingress Controller. | 1
125
125
`controller.image.repository` | The image repository of the Ingress controller. | nginx/nginx-ingress
126
-
`controller.image.tag` | The tag of the Ingress controller image. | 1.6.1
126
+
`controller.image.tag` | The tag of the Ingress controller image. | 1.6.2
127
127
`controller.image.pullPolicy` | The pull policy for the Ingress controller image. | IfNotPresent
128
128
`controller.config.name` | The name of the ConfigMap used by the Ingress controller. | Autogenerated
129
129
`controller.config.entries` | The entries of the ConfigMap for customizing NGINX configuration. | {}
0 commit comments