bzp2010 commented on issue #11953: URL: https://github.com/apache/apisix/issues/11953#issuecomment-2676361951
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). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
