From 5d7a30783f604e9fdf306b739744d373386d702c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=BE=84=E6=BD=AD?= Date: Sun, 4 Jan 2026 09:33:30 +0800 Subject: [PATCH] Update README.md --- README.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index f52a763d4..2846455e0 100644 --- a/README.md +++ b/README.md @@ -119,7 +119,16 @@ If you are deploying on the cloud, it is recommended to use the [Enterprise Edit Higress can function as a feature-rich ingress controller, which is compatible with many annotations of K8s' nginx ingress controller. - [Gateway API](https://gateway-api.sigs.k8s.io/) support is coming soon and will support smooth migration from Ingress API to Gateway API. + [Gateway API](https://gateway-api.sigs.k8s.io/) is already supported, and it supports a smooth migration from Ingress API to Gateway API. + + Compared to ingress-nginx, the resource overhead has significantly decreased, and the speed at which route changes take effect has improved by ten times. + + > The following resource overhead comparison comes from [sealos](https://github.com/labring). + > + > For details, you can read this [article](https://sealos.io/blog/sealos-envoy-vs-nginx-2000-tenants) to understand how sealos migrates the monitoring of **tens of thousands of ingress** resources from nginx ingress to higress. + + ![](https://img.alicdn.com/imgextra/i1/O1CN01bhEtb229eeMNBWmdP_!!6000000008093-2-tps-750-547.png) + - **Microservice gateway**: