sebschlue opened a new issue, #1880: URL: https://github.com/apache/apisix-ingress-controller/issues/1880
### Current Behavior I have deployed apisix ingress controller from latest Helm chart 2.0.0 and am playing with it for a few days now. CR objects like apisixRoute work fine but Ingress objects don't work. I noticed that "kubectl get ingressclass" does not list apisix as an ingress class. I also noticed that Ingress objects with spec: ingressClassName: apisix do not work. namespace_selector is set to "" so I believe it should work for all namespaces. I have checked possible missing helm chart settings for both apisix/apisix chart as well as apisix/apisix-ingress-controller chart but did not find any setting that would relate specifically to the ability to support Ingress objects. Also, the docs to not list any special requirements: https://apisix.apache.org/docs/ingress-controller/tutorials/proxy-the-httpbin-service-with-ingress/ I am sorry that I cannot offer any specific information as there are no error messages whatsover, it just does not work at all. Some information regarding my environment: k8s is AWS EKS 1.24, helm is 3.10.3 ### Expected Behavior Ingress objects should be "watched" and acted upon by apisix ingress controller if they specify ingressClassName apisix ### Error Logs Unfortunetely, none ### Steps to Reproduce Install APISIX ingress controller via Helm chart. Create Ingress object with ingressClassName apisix ### Environment chart-version: apisix/apix 2.0.0 with app-version 3.3.0 installs deployment- and statefulset-objects using the following container images: apache/apisix-ingress-controller:1.6.0 apache/apisix:3.3.0-debian bitnami/etcd:3.5.7-debian-11-r14 -- 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]
