gdevelek opened a new issue, #9772:
URL: https://github.com/apache/apisix/issues/9772
### Description
I have a multitude of issues using Apisix 3.3.0 with Bitnami etcd 3.5.7 and
Dashboard 3.0.0 on AWS EKS v1.24 (installed just fine with Helm chart 1.4.0).
The three critical ones are:
1. I cannot define routes using the ApisixRoute CRD. The CRD is defined in
K8s but the route is not visible in the dashboard and is not showing when I ask
for the entire list of routes using Curl.
2. I cannot define routes using the Ingress object, the ingressClassName
"apisix" is rejected.
3. When I define a route using a curl request, it works fine, but when I
export/import into another server, the upstream info disappears. This happens
whether I define the upstream in the curl request along with the front-end, or
I define both in separate requests and link them with upstream ID.
I'm not including YAML because it's code I have just copy-pasted from the
official docs.
There is documentation for everything, but in my opinion it skips steps and
makes assumptions that do not apply to people who experiment with APISIX for
the 1st time. This happens very often, doc writers cannot get out of their
shoes and into the shoes of a newcomer.
Plus I have been unable to find a tutorial with a complete walk-through,
which in my opinion is absolutely essential given the complexity of the subject
matter.
I hope I can get some pointers here.
### 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`):
--
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]
