idb-root commented on issue #9796:
URL: https://github.com/apache/apisix/issues/9796#issuecomment-1624954391

   > > > pisix is deployed in the K8S container cluster. When redeploying the 
container, Apisix reports 502. Is there any solution to avoid 502? Ps:
   > > 
   > > 
   > > Rolling deployment of containers on the K8S platform
   > > Ps:
   > > The container has a health check, but the upstream service of Apisix 
does not have a health check
   > > This is the real log returned by Apisix, and the sensitive parts have 
been replaced with xxx
   > 
   > Yes Bro. I think your cluster maybe just haven On Upstream such as One Pod 
or other for "http://x.xxx.com/"; . So In Your `redeploying the container` Times 
, The Backend Server is Unavailable. If there have any request ,It should be 
502 is normal.
   > 
   > you seems need have more Pod and degrade your `Unavailable` server via 
Active HealthCheck .
   > 
   > Hope tips have some help to you
   > 
   > <img alt="截屏2023-07-07 下午3 08 23" width="1074" 
src="https://user-images.githubusercontent.com/29942463/251665119-dc36c358-2ff3-4be8-8c9d-8fb2bbba5cf7.png";>
   
   
   English:
     When redeploying or publishing container groups on the K8S platform, 
elegant downtime was configured for the containers to avoid the occurrence of 
states such as 502
     I suspect that the 502 issue that occurred after using Apisix in the 
middle was caused by the strong disconnection of Apisix, but I am not sure how 
to configure Apisix to avoid it
   
   中文:
     在k8s平台重新部署或发布容器组的时候,对容器配置了优雅停机,而避免了502等状态的出现
     中间使用了apisix后而出现的502,我怀疑还是apisix出现的强断开导致的,但不清楚怎么配置apisix来避免
   
   ["/bin/bash","-c","sleep 60; curl -X POST -H 'Content-Type: 
application/json' http://localhost:8080/XXX/actuator/shutdown";]


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