Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update APISIX Ingress implementation status #2103

Merged
merged 1 commit into from
Jun 9, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions site-src/implementations.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Implementors and integrators of Gateway API are encouraged to update this docume

- [Acnodal EPIC][1] (public preview)
- [Amazon Elastic Kubernetes Service][23] (alpha)
- [Apache APISIX][2] (alpha)
- [Apache APISIX][2] (beta)
- [BIG-IP Kubernetes Gateway][20] (beta)
- [Cilium][16] (beta)
- [Contour][3] (beta)
Expand Down Expand Up @@ -81,7 +81,7 @@ Documentation can be found at [EPIC Application & API Gateway Service][epic]

[Apache APISIX][apisix] is a dynamic, real-time, high-performance API Gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more.

APISIX currently supports Gateway API `v1alpha2` version of the specification for its [Apache APISIX Ingress Controller][apisix-1].
APISIX currently supports Gateway API `v1beta1` version of the specification for its [Apache APISIX Ingress Controller][apisix-1].

[apisix]:https://apisix.apache.org/
[apisix-1]:https://github.com/apache/apisix-ingress-controller
Expand Down