-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
help request: Can APISIX 3.2.0 support Kubernetes version 1.28 and above #11953
Comments
+1 |
Hi NJUST friend, what is your issue? I'm still running 2.15.1 on my GKE 1.31. |
Hi @njustzsm, when running inside K8s 1.28+, what kind of issues you encountered? |
APISIX is not directly associated with any Kubernetes version, either as a function of the API gateway or the built-in Kubernetes service discovery (unless Kubernetes has modified its Endpoint functionality). APISIX can be run on most systems used for servers and tested on major systems. It supports container and bare metal deployments (containers should be considered first), and of course Kubernetes. If, however, you want to use the APISIX Ingress Controller, you should consider compatibility, but given that we're not introducing any incompatible updates at the moment, I'm assuming it's compatible with Kubernetes 1.28+.
By the way, it's now Feb 2025 and the 3.2 version has been out for more than two years, so there's no reason why you shouldn't be using an ancient version instead of the latest release of 3.11 if you don't have any existing deployments based on 3.2. This would ignore any efforts to introduce new features and improvements we've made, and put your service at potential risk. The 3.2 branch will no longer get any patch release, and bug reports there will not get a high-priority response unless they can be reproduced on the mainline release by reporter himself (Personally, I wouldn't spend another minute here; others will determine their own time). |
Description
Can APISIX 3.2.0 support Kubernetes version 1.28 and above
Environment
apisix version
):uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):The text was updated successfully, but these errors were encountered: