search

kubernetes / kubernetes

Production-Grade Container Scheduling and Management
https://kubernetes.io
Apache License 2.0
111.49k stars 39.77k forks source link

Ingress backend change results in 502 for GCE Ingress #44132

Closed brendandburns closed 6 years ago

brendandburns commented 7 years ago

I was switching an existing Ingress resource from one Kubernetes Service to a different Service

After I updated the Ingress object, the GCE L7 LB had 30-90 seconds of time where it was returning 502.

Perhaps this is a problem in the GCE L7 LB, but it seems like this shouldn't happen.

brendandburns commented 7 years ago

It's possible that this is because I was serving a 301 on the HTTP call which the GSLB interprets as "failing" a health check.

prasadpilla commented 7 years ago

@brendandburns I'm facing the same issue right now.

My app redirects requests at "/" to a login page. How did you solve it?

I defined liveness and readiness probes for my pod, still this happens.

fejta-bot commented 6 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 6 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten /remove-lifecycle stale

fejta-bot commented 6 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close