|
1 | 1 | # Changelog
|
2 | 2 |
|
| 3 | +### 1.8.0 |
| 4 | + |
| 5 | +OVERVIEW: |
| 6 | + |
| 7 | +Release 1.8.0 includes: |
| 8 | +* Support for NGINX App Protect Web Application Firewall. |
| 9 | +* Support for configuration snippets and custom template for VirtualServer and VirtualServerRoute resources. |
| 10 | +* Support for request/response header manipulation and request URI rewriting for VirtualServer/VirtualServerRoute. |
| 11 | +* Introducing a new configuration resource - Policy - with the first policy for IP-based access control. |
| 12 | + |
| 13 | +You will find the complete changelog for release 1.8.0, including bug fixes, improvements, and changes below. |
| 14 | + |
| 15 | +FEATURES FOR VIRTUALSERVER AND VIRTUALSERVERROUTE RESOURCES: |
| 16 | +* [1036](https://github.com/nginxinc/kubernetes-ingress/pull/1036): Add VirtualServer custom template support. |
| 17 | +* [1028](https://github.com/nginxinc/kubernetes-ingress/pull/1028): Add access control policy. |
| 18 | +* [1019](https://github.com/nginxinc/kubernetes-ingress/pull/1019): Add VirtualServer/VirtualServerRoute snippets support. |
| 19 | +* [1006](https://github.com/nginxinc/kubernetes-ingress/pull/1006): Add request/response modifiers to VS and VSR. |
| 20 | +* [994](https://github.com/nginxinc/kubernetes-ingress/pull/994): Support Class Field in VS/VSR. |
| 21 | +* [973](https://github.com/nginxinc/kubernetes-ingress/pull/973): Add status to VirtualServer and VirtualServerRoute. |
| 22 | + |
| 23 | +FEATURES: |
| 24 | +* [1035](https://github.com/nginxinc/kubernetes-ingress/pull/1035): Support for App Protect module. |
| 25 | +* [1029](https://github.com/nginxinc/kubernetes-ingress/pull/1029): Add readiness endpoint. |
| 26 | + |
| 27 | +IMPROVEMENTS: |
| 28 | +* [995](https://github.com/nginxinc/kubernetes-ingress/pull/995): Emit event for orphaned VirtualServerRoutes. |
| 29 | +* Documentation improvements: [946](https://github.com/nginxinc/kubernetes-ingress/pull/946) thanks to [谭九鼎](https://github.com/imba-tjd), [948](https://github.com/nginxinc/kubernetes-ingress/pull/948), [972](https://github.com/nginxinc/kubernetes-ingress/pull/972), [965](https://github.com/nginxinc/kubernetes-ingress/pull/965). |
| 30 | + |
| 31 | +BUGFIXES: |
| 32 | +* [1030](https://github.com/nginxinc/kubernetes-ingress/pull/1030): Fix port range validation in cli arguments. |
| 33 | +* [953](https://github.com/nginxinc/kubernetes-ingress/pull/953): Fix error logging of master/minion ingresses. |
| 34 | + |
| 35 | +HELM CHART: |
| 36 | +* The version of the helm chart is now 0.6.0. |
| 37 | +* Add new parameters to the Chart: `controller.appprotect.enable`, `controller.globalConfiguration.create`, `controller.globalConfiguration.spec`, `controller.readyStatus.enable`, `controller.readyStatus.port`, `controller.config.annotations`, `controller.reportIngressStatus.annotations`. Added in [1035](https://github.com/nginxinc/kubernetes-ingress/pull/1035), [1034](https://github.com/nginxinc/kubernetes-ingress/pull/1034), [1029](https://github.com/nginxinc/kubernetes-ingress/pull/1029), [1003](https://github.com/nginxinc/kubernetes-ingress/pull/1003) thanks to [RubyLangdon](https://github.com/RubyLangdon). |
| 38 | +* [1047](https://github.com/nginxinc/kubernetes-ingress/pull/1047) and [1009](https://github.com/nginxinc/kubernetes-ingress/pull/1009): Change how Helm manages the custom resource defintions (CRDs) to support installing multiple Ingress Controller releases. **Note**: If you're using the custom resources (`controller.enableCustomResources` is set to `true`), this is a breaking change. See the HELM UPGRADE section below for the upgrade instructions. |
| 39 | + |
| 40 | +CHANGES: |
| 41 | +* Update NGINX version to 1.19.1. |
| 42 | +* Update NGINX Plus to R22. |
| 43 | +* [1029](https://github.com/nginxinc/kubernetes-ingress/pull/1029): Add readiness endpoint. The Ingress Controller now exposes a readiness endpoint on port `8081` and the path `/nginx-ready`. The endpoint returns a `200` response after the Ingress Controller finishes the initial configuration of NGINX at the start. The pod template was updated to use that endpoint in a readiness probe. |
| 44 | +* [980](https://github.com/nginxinc/kubernetes-ingress/pull/980): Enable leader election by default. |
| 45 | + |
| 46 | +UPGRADE: |
| 47 | +* For NGINX, use the 1.8.0 image from our DockerHub: `nginx/nginx-ingress:1.8.0`, `nginx/nginx-ingress:1.8.0-alpine` or `nginx-ingress:1.8.0-ubi` |
| 48 | +* For NGINX Plus, please build your own image using the 1.8.0 source code. |
| 49 | +* For Helm, use version 0.6.0 of the chart. |
| 50 | + |
| 51 | +HELM UPGRADE: |
| 52 | + |
| 53 | +If you're using custom resources like VirtualServer and TransportServer (`controller.enableCustomResources` is set to `true`), after you run the `helm upgrade` command, the CRDs and the corresponding custom resources will be removed from the cluster. Before upgrading, make sure to back up the custom resources. After running the `helm upgrade` command, run `kubectl apply -f deployments/helm-chart/crds` to re-install the CRDs and then restore the custom resources. |
| 54 | + |
| 55 | +NOTES: |
| 56 | +* As part of installing a release, Helm will install the CRDs unless that step is disabled (see the [corresponding doc](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-helm/)). The installed CRDs include the CRDs for all Ingress Controller features, including the ones disabled by default (like App Protect with `aplogconfs.appprotect.f5.com` and `appolicies.appprotect.f5.com` CRDs). |
| 57 | + |
3 | 58 | ### 1.7.2
|
4 | 59 |
|
5 | 60 | CHANGES:
|
|
0 commit comments