We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I deployed the apisix ingress controller on the k8s cluster. Can I use apisix Dashboard to create ApisixRoute and ApisixUpstream?
The text was updated successfully, but these errors were encountered:
If you use the architecture with etcd
you can deploy both the apisix-ingress-controller and apisix-dashboard in the same cluster, use the same etcd;
and the resources maintained by the APISIX Ingress Controller come with the description:
Created by apisix-ingress-controller, DO NOT modify it manually
and you can add route/service/upstream on the dashboard and it works.
If you use the new architecture without etcd, you can do nothing via apisix-dashboard.
Sorry, something went wrong.
如果你使用带有 etcd 的架构 您可以在同一个集群中部署 apisix-ingress-controller 和 apisix-dashboard,使用同一个 etcd; APISIX Ingress Controller 维护的资源附带以下描述: Created by apisix-ingress-controller, DO NOT modify it manually 您可以在仪表板上添加路线/服务/上游,它可以工作。 如果您使用没有 etcd 的新架构,您将无法通过 apisix-dashboard 执行任何操作。
如果你使用带有 etcd 的架构
您可以在同一个集群中部署 apisix-ingress-controller 和 apisix-dashboard,使用同一个 etcd;
APISIX Ingress Controller 维护的资源附带以下描述:
您可以在仪表板上添加路线/服务/上游,它可以工作。
如果您使用没有 etcd 的新架构,您将无法通过 apisix-dashboard 执行任何操作。
不错,跟我了解的一样。确实是这样。
No branches or pull requests
Issue description
I deployed the apisix ingress controller on the k8s cluster. Can I use apisix Dashboard to create ApisixRoute and ApisixUpstream?
Environment
The text was updated successfully, but these errors were encountered: