https://pulumi.com logo
Title
b

bland-cat-29878

07/16/2021, 1:07 PM
Hi - I have a strange issue where by when a deployment completes, the ingress temporarily returns 503 for services which are running - does anyone else see this? It clears after a few refreshes but that's obviously not ideal
b

brave-planet-10645

07/16/2021, 1:19 PM
Where are you deploying this to? (obviously k8s, but where is the cluster located)
b

bland-cat-29878

07/16/2021, 1:20 PM
my own servers
b

brave-planet-10645

07/16/2021, 1:23 PM
All I think of then is that the ingress is taking a little bit of time to find the services, and it's taking longer than the cluster is taking to switch out the containers
The reason I asked the deployment location is because I've seen this very occasionally when deploying to something behind AWS ALBs
b

bland-cat-29878

07/16/2021, 1:26 PM
does it matter that all of the ingress resources are in the ingress-nginx namespace and all of my services are in another? That's how it should work right?
b

brave-planet-10645

07/16/2021, 2:55 PM
yeah that's fine. That's how i've got some of mine setup
s

sparse-park-68967

07/16/2021, 4:50 PM
assume you have readiness probes and min availability etc. defined for your deployment? sounds like your backing endpoints might have no pods to map to.
👍 1
b

bland-cat-29878

07/19/2021, 7:52 AM
yep - liveness, readiness, rolling update strategy etc - still no dice