nginxinc/kubernetes-ingress v1.8.0

NGINX Ingress Controller 1.8.0

on GitHub

🚀 Help make the NGINX Ingress Controller better by participating in our survey! 🚀

OVERVIEW:

Release 1.8.0 includes:

• Support for NGINX App Protect Web Application Firewall.
• Support for configuration snippets and custom template for VirtualServer and VirtualServerRoute resources.
• Support for request/response header manipulation and request URI rewriting for VirtualServer/VirtualServerRoute.
• Introducing a new configuration resource - Policy - with the first policy for IP-based access control.

You will find the complete changelog for release 1.8.0, including bug fixes, improvements, and changes below.

FEATURES FOR VIRTUALSERVER AND VIRTUALSERVERROUTE RESOURCES:

• 1036: Add VirtualServer custom template support.
• 1028: Add access control policy.
• 1019: Add VirtualServer/VirtualServerRoute snippets support.
• 1006: Add request/response modifiers to VS and VSR.
• 994: Support Class Field in VS/VSR.
• 973: Add status to VirtualServer and VirtualServerRoute.

FEATURES:

• 1035: Support for App Protect module.
• 1029: Add readiness endpoint.

IMPROVEMENTS:

• 995: Emit event for orphaned VirtualServerRoutes.
• Documentation improvements: 946 thanks to 谭九鼎, 948, 972, 965.

BUGFIXES:

• 1030: Fix port range validation in cli arguments.
• 953: Fix error logging of master/minion ingresses.

HELM CHART:

• The version of the helm chart is now 0.6.0.
• 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, 1034, 1029, 1003 thanks to RubyLangdon.
• 1047 and 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.

CHANGES:

• Update NGINX version to 1.19.1.
• Update NGINX Plus to R22.
• 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.
• 980: Enable leader election by default.

UPGRADE:

• 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
• For NGINX Plus, please build your own image using the 1.8.0 source code.
• For Helm, use version 0.6.0 of the chart.

HELM UPGRADE:

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.

NOTES:

• As part of installing a release, Helm will install the CRDs unless that step is disabled (see the corresponding doc). 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).

RESOURCES:

• Documentation -- https://docs.nginx.com/nginx-ingress-controller/
• Configuration examples -- https://github.com/nginxinc/kubernetes-ingress/tree/v1.8.0/examples and https://github.com/nginxinc/kubernetes-ingress/tree/v1.8.0/examples-of-custom-resources
• Helm Chart -- https://github.com/nginxinc/kubernetes-ingress/tree/v1.8.0/deployments/helm-chart
• Operator -- https://github.com/nginxinc/nginx-ingress-operator/