K
Q

Google Cloud Kubernetes Nginx Ingress hang on "Creating ingress"

6/27/2018

When creating an ingress resource in GCE using the Nginx ingress controller, the ingress resource is stuck on "Creating ingress". Any custom annotations appear to be lost, but I can access the URL defined by the ingress.

What could be causing this?

enter image description here

-- Phyxx
kubernetes
nginx

Similar Questions

kubectl describe node does not report proper pod usage
Does kubernetes come with docker by default
Docker image not copying files names starting with
Logging for Kubernetes Calico NetworkPolicy?
Using cert-manager to pull secrets from external store and only issue new cert if expired
CORS issue during GET and POST with an HTTPS API hosted on Azure Kubernetes Service
Kubernetes NetworkPlugin error: route already exists for an interface other than
Best solution to deploy geth(go-ethereum) on kubernetes(aws eks)

2 Answers

7/26/2019

For anyone in the same situation in GKE, just go to the console and click on "Services and Ingress" and click on the Ingress to see a possible error.

Mine was a misspelled service name.

I had to delete the Ingress and re-apply the ingress manifest (kubectl apply -f my-ingress.yaml)

-- Guillermo
Source: StackOverflow
6/27/2018

This turned out to be because I was sending the annotation

nginx.ingress.kubernetes.io/ssl-redirect: false

instead of

nginx.ingress.kubernetes.io/ssl-redirect: "false"

According to https://github.com/kubernetes/ingress-nginx/issues/1990, the Nginx controller only accepts strings containing "true" or "false". By sending boolean values, GCE was hanging.

Interestingly there were no errors indicating a problem, and I could access the ingress URL, which made debugging the problem quote painful.

-- Phyxx
Source: StackOverflow