You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "Baoyuantop (via GitHub)" <gi...@apache.org> on 2026/04/08 09:50:41 UTC

Re: [I] request help: etcd-0 CrashLoopBackOff [apisix-helm-chart]

Baoyuantop commented on issue #414:
URL: https://github.com/apache/apisix-helm-chart/issues/414#issuecomment-4205367673

   The etcd `CrashLoopBackOff` issue is typically an etcd operational problem (storage, DNS, resource constraints) rather than a Helm chart defect. If the APISIX functions work normally despite the etcd pod errors, it may indicate the etcd cluster recovered after initial failures.
   
   Common troubleshooting steps:
   1. Check etcd logs: `kubectl logs etcd-0 -n your-namespace`
   2. Verify storage: `kubectl get pvc -n your-namespace`
   3. Check resource limits for the etcd pods
   
   Closing as this is an environment/operations issue. If you still experience this with the current chart version, please feel free to reopen with detailed logs.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org