-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nginx-ingress: occasional 503 Service Temporarily Unavailable #821
Comments
I sometimes see the same problem and my guess is the controller does not pick up updated/new ingress rules populated in the meantime. (I think this started happening for me when going from The only thing working for me was to gradually restart the old nginx-ingress instances. The fresh ones work as expected. Here is a bash-script, which does these restarts: #!/bin/bash -
set -o nounset
BASE=$(cd "$(dirname "$0")" && pwd)
pushd "${BASE}"
for i in $(kubectl get pods -n kube-system | grep nginx-ingress-lb | awk '{print $1}')
do
echo "will kill ${i}"
kubectl delete "pod/${i}" -n kube-system
echo "Waiting 30 seconds for new pod to come up before killing next old pod..."
sleep 30
done |
@weitzj please update the image to |
@troian the fix for 768 and PRs 822, 823 and 824 |
@aledbf Your image The steps I took:
Btw.: The nginx controller runs using the |
@aledbf thanks The issue I wonder is why it produces Fake certificate even if --default-ssl-certificate specified in argument and ingress contains only one domain with same certificate chain |
@troian I also see these 503 timeouts with the current |
There is nothing we can do to avoid 503 in that situation |
Seems image quay.io/aledbf/nginx-ingress-controller:0.132 helps. |
We had intermittent 503 errors which might be connected to kubernetes/ingress-nginx#821 [#148743365] Signed-off-by: Brendan Nolan <bnolan@pivotal.io>
works then for minikube as well with
|
I'm experiencing often 503 response from nginx-ingress-controller which returns as well
Kubernetes Ingress Controller Fake Certificate (2) instead of provided wildcard certificate.
Image is gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.7
Looks like at some point nginx cannot resolve proper server_name and returns fake. But then why it ignores --default-ssl-certificate argument.
Anyway I'm out of thoughts thus any help appreciated
Cluster is running at GKE
The text was updated successfully, but these errors were encountered: