Skip to content

Commit e3a101b

Browse files
committed
Clarify Higress as third-party integration
Add clear designation that Higress integration is third-party and not managed by the Knative community, as requested by reviewers. Change-Id: I98d3454da8a8e4cef74ac5a88d8b0f3017426c15 Co-developed-by: Cursor <noreply@cursor.com>
1 parent b94738b commit e3a101b

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

docs/versioned/install/README.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,9 +101,12 @@ If you don't have an ingress that meets the requirements, Knative provides [net-
101101

102102
The Kubernetes [Gateway API](https://kubernetes.io/docs/concepts/services-networking/gateway/) (beta).
103103

104-
- Higress
104+
- Higress (Third-party integration)
105105

106106
A next-generation cloud-native gateway that integrates traffic management, security protection, and microservices capabilities. Higress provides enhanced traffic governance, authentication, WAF protection, and observability for Knative services with WASM plugin extensibility. See [Higress: A Best Practice for Knative Ingress Gateway](https://www.alibabacloud.com/blog/higress-a-best-practice-for-knative-ingress-gateway_600549).
107+
108+
!!! note
109+
This integration is not managed by the Knative community.
107110

108111
### Messaging plugins
109112

0 commit comments

Comments
 (0)