software engineer

> etcd failure is very likely a problem with etcd itself. Did you check my screenshot ? As you know two of instances are running but I can't know why...

> It clearly says CrashLoopBackOff which means that the image is unable to get pulled successfully even after multiple tries. Did you check if you're using the correct image name...

kubectl logs apisix-etcd-0 --namespace api-apisix  kubectl logs apisix-etcd-1 --namespace api-apisix  kubectl logs apisix-etcd-2 --namespace api-apisix  kubectl logs apisix-5d7754c6c4-pxnnj --namespace api-apisix 

> Hi, Can you share the logs? plz check

I have followed the instruction. could you tell me where the reason is ?

> The problem is that the image is unable to get pulled successfully. Also check if your etcd is working perfectly and there is no address bind. I have followed...

this is the guide from apisix due to this error, I have reinstalled with this guide but all pods is not running  https://apisix.apache.org/blog/2021/12/15/deploy-apisix-in-kubernetes/ using kubectl describe pod pod_name --n...

> Can you check the reason about why etcd `apisix-etcd-0` not running ? Could you please check the errors ? It is a little challenge from me. I hope you...

> ETCD_ADVERTISE_CLIENT_URLS > Yes, the etcd cluster is not running normal. So you can scale etcd replicas from 3 to 1 . Or you can try preference etcd cluster config...

this is my pod yaml using kubectl edit command for the pod but it seems different with your config - name: etcd image: docker.io/bitnami/etcd:3.5.7-debian-11-r14 ports: - name: client containerPort: 2379...