This topic introduces the NGINX Ingress controller and describes the usage notes and release notes for the NGINX Ingress controller.
Introduction
Introduction to Ingress
In a Kubernetes cluster, an Ingress functions as an access point that exposes Services in the cluster. It distributes most of the network traffic that is destined for the Services in the cluster. An Ingress is a Kubernetes resource object that is used to enable external access to Services in a Kubernetes cluster. You can configure routing rules for an Ingress to route network traffic to backend pods of different Services.
How the NGINX Ingress controller works
Ingresses can work as normal only if you deploy an NGINX Ingress controller in the cluster to parse the routing rules of the Ingresses. After the NGINX Ingress controller receives a request that matches a routing rule, the NGINX Ingress controller routes the request to a corresponding backend Service. The backend Service then forwards the request to pods. In a Kubernetes cluster, Services, Ingresses, and the NGINX Ingress controller work in the following process:
A Service is an abstraction of a backend application that runs on a set of replicated pods.
An Ingress contains reverse proxy rules. It controls to which Service pods HTTP or HTTPS requests are routed. For example, requests are routed to different Service pods based on the hosts and URL paths in the requests.
The NGINX Ingress controller is a reverse proxy program that parses Ingress rules. If changes are made to the Ingress rules, the NGINX Ingress controller updates the Ingress rules accordingly. After the NGINX Ingress controller receives a request, it redirects the request to Service pods based on the Ingress rules.
Usage notes
For more information about how to use the NGINX Ingress controller, see Use the NGINX Ingress controller to implement canary releases and blue-green releases and Use an Ingress controller to mirror network traffic.
Release notes
June 2023
Version | Image address | Release date | Description |
v1.8.0-aliyun.1 | registry-cn-hangzhou.ack.aliyuncs.com/acs/aliyun-ingress-controller:v1.8.0-aliyun.1 | 2023-06-20 |
|
May 2023
Version | Image address | Release date | Description | Impact |
v1.7.0-aliyun.1 | registry-cn-hangzhou.ack.aliyuncs.com/acs/aliyun-ingress-controller:v1.7.0-aliyun.1 | 2023-05-05 | Important TLS v1.1 and TLS v1.0 are no longer supported by this version. If you update the NGINX Ingress controller to this version, pay attention to the impact on your businesses. For more information about the impact of this issue, see set ssl-protocols config not working after v1.6.4.
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
March 2023
Version | Image address | Release date | Description | Impact |
v1.6.4-aliyun.1 | registry-cn-hangzhou.ack.aliyuncs.com/acs/aliyun-ingress-controller:v1.6.4-aliyun.1 | 2023-03-17 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
February 2023
Version | Image address | Release date | Description | Impact |
v1.5.1-aliyun.1 | registry-cn-hangzhou.ack.aliyuncs.com/acs/aliyun-ingress-controller:v1.5.1-aliyun.1 | 2023-02-10 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
June 2022
Version | Image address | Release date | Description | Impact |
v1.2.1-aliyun.1 | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v1.2.1-aliyun.1 | 2022-06-28 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
May 2022
Version | Image address | Release date | Description | Impact |
v1.2.0-aliyun.1 | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v1.2.0-aliyun.1 | 2022-05-10 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
April 2022
Version | Image address | Release date | Description | Impact |
v0.44.0.12-27ae67262-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.44.0.12-27ae67262-aliyun | 2022-04-29 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
March 2022
Version | Image address | Release date | Description | Impact |
v1.1.2-aliyun.2 | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v1.1.2-aliyun.2 | 2022-03-21 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
January 2022
Version | Image address | Release date | Description | Impact |
v1.1.0-aliyun.2 | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v1.1.0-aliyun.2 | 2022-01-12 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
December 2021
Version | Image address | Release date | Description | Impact |
v1.1.0-aliyun.1 | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v1.1.0-aliyun.1 | 2021-12-17 |
For more information, see Ingress-NGINX changelog. | The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
October 2021
Version | Image address | Release date | Description | Impact |
v0.44.0.9-7b9e93e7e-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.44.0.9-7b9e93e7e-aliyun | 2021-10-28 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
September 2021
Version | Image address | Release date | Description | Impact |
v0.44.0.5-e66e17ee3-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.44.0.5-e66e17ee3-aliyun | 2021-09-06 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
June 2021
Version | Image address | Release date | Description | Impact |
v0.44.0.3-8e83e7dc6-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.44.0.3-8e83e7dc6-aliyun | 2021-06-01 | Vulnerability CVE-2021-23017 is fixed. For more information, see Updating NGINX for a DNS Resolver Vulnerability (CVE-2021-23017). | The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
April 2021
Version | Image address | Release date | Description | Impact |
v0.44.0.2-abf1c6fe4-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.44.0.2-abf1c6fe4-aliyun | 2021-04-01 | Compatibility with the | The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
March 2021
Version | Image address | Release date | Description | Impact |
v0.44.0.1-5e842447b-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.44.0.1-5e842447b-aliyun | 2021-03-08 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
April 2020
Version | Image address | Release date | Description | Impact |
v0.30.0.1-5f89cb606-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.30.0.1-5f89cb606-aliyun | 2020-04-02 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
October 2019
Version | Image address | Release date | Description | Impact |
v0.22.0.5-552e0db-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.22.0.5-552e0db-aliyun | 2019-10-24 | Wildcard domain names, whitelists, and rewrite rules are supported if you enable dynamic updates for NGINX upstream servers. | The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
July 2019
Version | Image address | Release date | Description | Impact |
v0.22.0.4-5a14d4b-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.22.0.4-5a14d4b-aliyun | 2019-07-18 | Canary release rules are optimized and the Perl regular expressions are supported. | The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
April 2019
Version | Image address | Release date | Description | Impact |
v0.22.0.3-da10b7f-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.22.0.3-da10b7f-aliyun | 2019-04-25 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
January 2019
Version | Image address | Release date | Description | Impact |
v0.20.0.2-cc39f1b-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.20.0.2-cc39f1b-aliyun | 2019-01-17 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |
November 2018
Version | Image address | Release date | Description | Impact |
v0.20.0.1-4597ce2-aliyun | registry.cn-hangzhou.aliyuncs.com/acs/aliyun-ingress-controller:v0.20.0.1-4597ce2-aliyun | 2018-11-29 |
| The update may temporarily interrupt your service. We recommend that you update the NGINX Ingress controller during off-peak hours. |