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

help request: Can APISIX 3.2.0 support Kubernetes version 1.28 and above #11953

Open
njustzsm opened this issue Feb 7, 2025 · 4 comments
Open
Labels
question label for questions asked by users

Comments

@njustzsm
Copy link

njustzsm commented Feb 7, 2025

Description

Can APISIX 3.2.0 support Kubernetes version 1.28 and above

Environment

  • APISIX version (run apisix version):
  • Operating system (run uname -a):
  • OpenResty / Nginx version (run openresty -V or nginx -V):
  • etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
  • APISIX Dashboard version, if relevant:
  • Plugin runner version, for issues related to plugin runners:
  • LuaRocks version, for installation issues (run luarocks --version):
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Apache APISIX backlog Feb 7, 2025
@dosubot dosubot bot added the question label for questions asked by users label Feb 7, 2025
@cataglyphis
Copy link

+1

@xgenvn
Copy link

xgenvn commented Feb 9, 2025

Hi NJUST friend, what is your issue? I'm still running 2.15.1 on my GKE 1.31.

@juzhiyuan
Copy link
Member

Hi @njustzsm, when running inside K8s 1.28+, what kind of issues you encountered?

@bzp2010
Copy link
Contributor

bzp2010 commented Feb 22, 2025

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+.

Any publicly available bug reports can be accessed via issue, and if any match your scenario, then you should consider mentioning the issue.


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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question label for questions asked by users
Projects
Status: 📋 Backlog
Development

No branches or pull requests

5 participants