8thblock opened a new issue #153: URL: https://github.com/apache/apisix-helm-chart/issues/153
Evaluating APISIX to replace our NGINX ingress and it does not seem to work on Kubernetes cluster that comes as a default with Docker Desktop Here are the details: OS: mac OS Env: k8s that comes with docker desktop Installed by: `cd /path/to/apisix-helm-chart helm repo add bitnami https://charts.bitnami.com/bitnami helm repo update kubectl create ns ingress-apisix helm install apisix charts/apisix \ --set gateway.type=NodePort \ --set ingress-controller.enabled=true \ --namespace ingress-apisix kubectl get service --namespace ingress-apisix` Everything installed ok: `NAME READY STATUS RESTARTS AGE pod/apisix-56c976fc-jrf6l 1/1 Running 0 49m pod/apisix-etcd-0 1/1 Running 0 49m pod/apisix-etcd-1 1/1 Running 0 49m pod/apisix-etcd-2 1/1 Running 0 49m pod/apisix-ingress-controller-b5f5d49db-6fp7n 1/1 Running 0 49m pod/httpbin 1/1 Running 0 33m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/apisix-admin ClusterIP 10.104.186.82 <none> 9180/TCP 49m service/apisix-etcd ClusterIP 10.101.172.59 <none> 2379/TCP,2380/TCP 49m service/apisix-etcd-headless ClusterIP None <none> 2379/TCP,2380/TCP 49m service/apisix-gateway NodePort 10.106.23.81 <none> 80:31205/TCP 49m service/apisix-ingress-controller ClusterIP 10.110.119.97 <none> 80/TCP 49m service/httpbin ClusterIP 10.96.245.203 <none> 80/TCP 33m NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/apisix 1/1 1 1 49m deployment.apps/apisix-ingress-controller 1/1 1 1 49m NAME DESIRED CURRENT READY AGE replicaset.apps/apisix-56c976fc 1 1 1 49m replicaset.apps/apisix-ingress-controller-b5f5d49db 1 1 1 49m NAME READY AGE statefulset.apps/apisix-etcd 3/3 49m` However: No routes are registering if I try and upon close inspection I noticed there are plenty of errors in the ingress controller. See attached logs. Is there anything that I am missing? Just followed your docs and got the latest helm [errors.log](https://github.com/apache/apisix-helm-chart/files/7315850/errors.log) -- 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]
