Discontinuing Update of NginxIngress Addon
Last updated: 2025-06-20 10:16:06
The NginxIngress Addon of TKE stopped iterating new versions and introducing features in June 2024 and will stop creating NginxIngress instances from October 1, 2024. Existing NginxIngress instances will continue to run, and will no longer be compatible with TKE 1.30 and later versions in the future. At that time, if instances using the NginxIngress Addon remain in the cluster, it will affect the upgrade of the cluster to 1.30 version.
If you need to upgrade your cluster to 1.30 or later versions, you can delete the installed NginxIngress addon on the component middle platform page. The deletion will not reclaim existing nginx-ingress-controller instances, but the cluster upgrade process will no longer verify the version of nginx-ingress-controller. You need to manually ensure the compatibility between versions of existing instances and the Kubernetes version. For configuration and upgrade of existing instances, see community documentation and Supported Versions table.
If you still need to use the monitoring and alarm feature of NginxIngress, see the community documentation to manually configure monitoring data collection and Grafana dashboard. In addition, if log collection is configured for NginxIngress, you need to configure log rotation manually to prevent the disk from being full.
If you still need to use NginxIngress, it is recommended to migrate instances to a self-built NginxIngress. You can see the Self-Built Nginx Ingress Practice Tutorial series documentation for migration.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback