You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "Richard0706 (via GitHub)" <gi...@apache.org> on 2025/12/13 14:45:11 UTC

[I] request help: How can I configure it to work like the old version? too difficult to use! [apisix-ingress-controller]

Richard0706 opened a new issue, #2679:
URL: https://github.com/apache/apisix-ingress-controller/issues/2679

   ### Issue description
   
   I'm unable to configure ingress across namespaces, even though I specified `ingressClassName: apisix` in the configuration; however, I can't see the new data in etcd and dashboard, which is completely different from the old version.
   The simplest ingress configuration below only works within the apisix ns;
   Even routes created in nsapisix cannot display the domain in the dashboard, which is unbelievable.
   
   `kind: Ingress
   apiVersion: networking.k8s.io/v1
   metadata:
     name: apisix-web
     namespace: apisix
     annotations:
       kubesphere.io/alias-name: apisix-web
       kubesphere.io/creator: admin
   spec:
     ingressClassName: apisix
     rules:
       - host: apisix-dashbord.test.com
         http:
           paths:
             - path: /*
               pathType: ImplementationSpecific
               backend:
                 service:
                   name: apisix-apisix-dashboard
                   port:
                     number: 80`
   
   <img width="1359" height="388" alt="Image" src="https://github.com/user-attachments/assets/1d0005cc-d654-4cf2-9e19-f9dd42c09933" />
   
   ### Environment
   
   - your apisix-ingress-controller version (output of apisix-ingress-controller version --long):2.0.0-rc5
   - your Kubernetes cluster version (output of kubectl version):v1.21.14
   - if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):
   **use chart:https://github.com/apache/apisix-helm-chart/releases/tag/apisix-2.12.4**


-- 
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: notifications-unsubscribe@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] request help: How can I configure it to work like the old version? too difficult to use! [apisix-ingress-controller]

Posted by "juzhiyuan (via GitHub)" <gi...@apache.org>.
juzhiyuan closed issue #2679: request help:  How can I configure it to work like the old version? too difficult to use!
URL: https://github.com/apache/apisix-ingress-controller/issues/2679


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] request help: How can I configure it to work like the old version? too difficult to use! [apisix-ingress-controller]

Posted by "Baoyuantop (via GitHub)" <gi...@apache.org>.
Baoyuantop commented on issue #2679:
URL: https://github.com/apache/apisix-ingress-controller/issues/2679#issuecomment-3654307654

   Hi @Richard0706, please confirm that you have configured GatewayProxy correctly. https://apisix.apache.org/docs/ingress-controller/upgrade-guide/#new-configuration-via-gatewayproxy-crd


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] request help: How can I configure it to work like the old version? too difficult to use! [apisix-ingress-controller]

Posted by "juzhiyuan (via GitHub)" <gi...@apache.org>.
juzhiyuan commented on issue #2679:
URL: https://github.com/apache/apisix-ingress-controller/issues/2679#issuecomment-3659260367

   Hi @Richard0706,
   
   From the screenshot, it appears that you are using an old version of APISIX Dashboard (antd-based) with APISIX Ingress Controller 2.0.
   
   1. We don't plan to extend support for the old dashboard.
   2. The new dashboard is bundled by default with apache/apisix since version 3.13+.
   3. If you want to use the new Ingress Controller, even in ETCD mode, we cannot promise that it will work with the old or new dashboard. This is outside the scope of our support. Refer to https://github.com/apache/apisix-dashboard/issues/2981


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org