techcheckri commented on issue #10774:
URL: https://github.com/apache/apisix/issues/10774#issuecomment-1884268684

   Problem is as could be seen before one can not get logs of terminated pods.
   
   ```
   kubectl -n ingress-apisix logs -f apisix-etcd-0 -p
   Error from server (BadRequest): previous terminated container "etcd" in pod 
"apisix-etcd-0" not found
   ```
   
   So what I can interpret from your statement is that etcd completed is 
abnormal behavior rather than just having finished a job normally as conveyed 
by the exit code 0. As seen exit code was 0:
   
   ```
   Name:             apisix-etcd-1
   Namespace:        ingress-apisix
   Priority:         0
   Service Account:  default
       State:          Terminated
         Reason:       Completed
         Exit Code:    0
   ```
   Abnormal termination should have some kind of error code or at least not 
stop with 0, right?
   
   So should the observed behavior of my etcd pods then not be seen as a bug 
and this report here be a bug report rather than a help request?
   


-- 
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]

Reply via email to