Open wofr opened 1 year ago
Does 0.11.1 work fine?
I think you should update the CRD file manually
I did not try 0.11.1, I will do it by now.
I dropped the whole deployment of apisix so the CRDs version should be fine
With 0.11.1 its working!
One funny observation I made, is that with 0.11.1 (and 0.11.0) the following call ist working and it does return the routes
kubectl exec -n apisix deploy/apisix-staging -- curl -s http://127.0.0.1:9180/apisix/admin/routes -H 'X-API-Key: MySecret'
With 0.11.2 (and 0.11.3)
kubectl exec -n apisix deploy/apisix-staging -- curl -s http://127.0.0.1:9180/apisix/admin/routes -H 'X-API-Key: MySecret'
I got the following error
error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "02bd185efd8594fb2e761f877be8974876c6b940701b3bc4be5d6496c552dd0b": OCI runtime exec failed: exec failed: unable to start container process: exec: "curl": executable file not found in $PATH: unknown
Description
The following routes works fine when I use apisix 0.11.0 (helm deplyoment). I do the deplyoment of the route in a declarative way. When I switch to use apisxi 0.11.3 or 0.11.2 the deplyoment does not work anymore. The only adaption I did on the route was use (apiVersion: apisix.apache.org/v2 instead of v2beta3)
Here the simple demo route I would like to deploy.
Environment
apisix version
): /usr/local/openresty/luajit/bin/luajit ./apisix/cli/apisix.lua version 2.15.1uname -a
): Linux apisix-staging-8589bc6d9-w26wt 5.10.133+ apache/apisix#1 SMP Sat Sep 10 14:54:12 UTC 2022 x86_64 GNU/Linuxopenresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):