Repository navigation
503 during blue-green deployment #4096
Unanswered
jan-machacek-kosik
asked this question in
Q&A
Replies: 1 comment
|
hey @jan-machacek-kosik this sounds like #4564 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We get 503 errors during deployment as all members are temporarily in unhealthy state.
We tried setting ignore_new_hosts_until_first_hc to false but it didn't help.
We know pods are succesfully deployed because we have rigorous startup/liveness/readiness probes and Argo Rollout analysis before we switch blue-green versions.
When we disable active healthcheck everything works fine.
Any idea what could be the cause?
We are trying to achieve zero-downtime blue-green deployment with active healthchecks for our microservices using Envoy as a Gateway.
Cluseter configuration:
All reactions