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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
