Open tranbaokhanh opened 2 years ago
kubectl port-forward
to expose the service to your localhost, so that you can access it.NodePort
so that you can access it through Kubernetes worker nodes' IP addresses;LoadBalancer
, so AWS will assign an ELB address for you, and you can access it on the Internet;@tokers how to set the apisix dashboard svc type to Nodeport?
i use this cmd:
helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=false --set dashboard.enabled=true --set dashboard.type=NodePort --set etcd.persistence.size=15G --set etcd.persistence.enabled=true --set etcd.volumePermissions.enabled=true --set admin.allow.ipList="" --namespace apisix
But that incorrect.
@tokers Thanks for your advice. i got it. BTW i have one more prbl. According this cmd #
@tokers how to set the apisix dashboard svc type to Nodeport? i use this cmd:
helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=false --set dashboard.enabled=true --set dashboard.type=NodePort --set etcd.persistence.size=15G --set etcd.persistence.enabled=true --set etcd.volumePermissions.enabled=true --set admin.allow.ipList="" --namespace apisix
But that incorrect.
i have check https://github.com/apache/apisix-helm-chart/issues/105#issuecomment-864813598 and set etcd.volumePermissions.enabled=true
but it dont auto create pv on my Nodes
i follow Setting up a High-availability RKE Kubernetes Cluster
https://rancher.com/docs/rancher/v2.6/en/installation/resources/k8s-tutorials/ha-rke/
@tokers Thanks for your advice. i got it. BTW i have one more prbl. According this cmd
@tokers how to set the apisix dashboard svc type to Nodeport? i use this cmd:
helm install apisix apisix/apisix --set gateway.type=NodePort --set ingress-controller.enabled=false --set dashboard.enabled=true --set dashboard.type=NodePort --set etcd.persistence.size=15G --set etcd.persistence.enabled=true --set etcd.volumePermissions.enabled=true --set admin.allow.ipList="" --namespace apisix
But that incorrect.i have check #105 (comment) and set
etcd.volumePermissions.enabled=true
but it dont auto create pv on my Nodes i follow Setting up a High-availability RKE Kubernetes Cluster https://rancher.com/docs/rancher/v2.6/en/installation/resources/k8s-tutorials/ha-rke/
I don't have too much experience for the use of RKE, maybe you can throw the question to Rancher community.
You can access it using the SVC internal domain name of k8s, which should be the simplest. You can also enable the dashboard's ingress configuration and configure the ingress class to apisix, but this configuration can be relatively complex
The format of the SVC domain name for k8s is: {service-name}.{namespace-name}.svc.{cluster-domain}
Assuming the service name of your dashboard is apisix-dashboard, the deployed namespace is ingress-apisix, and the cluster domain of your k8s cluster is cluster.local, then your dashboard domain name is:
apisix-dashboard.ingress-apisix.svc.cluster.local
For details, please refer to the documentation of k8s: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
Localhost: If you're running the dashboard locally, you can visit this URL: http://localhost:9000/user/login
.
Kubernetes: If you're using Kubernetes, you can set the app six-dashboard service type to NodePort so that you can access it through Kubernetes worker nodes' IP addresses. If you're using a managed Kubernetes service like EKS, you can set the app six-dashboard service type to LoadBalancer, so AWS will assign an ELB address for you, and you can access it on the Internet.
Shell or Service: You can run the dashboard in the shell with sudo manager-api -p /usr/local/apisix/dashboard/
or run the dashboard as a service with systemctl start apisix-dashboard
.
Remember to replace /usr/local/apisix/dashboard/
with your actual APISIX Dashboard path if it's different.
I have a cluster. i install APISIX via Helm with:
kubectl get pods -o wide -n apisix
kubectl get svc -n apisix
So, How to browser to the apisix-dashboard