14

When creating ingress, no address is generated and when viewed from GKE dashboard it is always in theCreating ingress status.Describing the ingress does not show any events and I can not see any clues on GKE dashboard.

Has anyone has a similar issue or any suggestions on how to debug?

My deployment.yaml

apiVersion: extensions/v1beta1kind: Ingressmetadata:  name: mobile-gateway-ingress    spec:  backend:    serviceName: mobile-gateway-service    servicePort: 80---apiVersion: v1kind: Servicemetadata:  name: mobile-gateway-servicespec:  ports:  - protocol: TCP    port: 80    targetPort: 8080  selector:    app: mobile-gateway  type: NodePort---apiVersion: apps/v1 kind: Deploymentmetadata:  name: mobile-gateway-deployment  labels:    app: mobile-gatewayspec:  selector:    matchLabels:      app: mobile-gateway  replicas: 2  template:    metadata:      labels:        app: mobile-gateway    spec:      containers:      - name: mobile-gateway        image: eu.gcr.io/my-project/mobile-gateway:latest        ports:          - containerPort: 8080

Describing ingress shows no events:

mobile-gateway ➤ kubectl describe ingress mobile-gateway-ingress                                                                                                                         git:master*Name:             mobile-gateway-ingressNamespace:        defaultAddress:Default backend:  mobile-gateway-service:80 (10.4.1.3:8080,10.4.2.3:8080)Rules:  Host  Path  Backends  ----  ----  --------  *     *     mobile-gateway-service:80 (10.4.1.3:8080,10.4.2.3:8080)Annotations:  kubectl.kubernetes.io/last-applied-configuration:  {"apiVersion":"extensions/v1beta1","kind":"Ingress","metadata":{"annotations":{},"name":"mobile-gateway-ingress","namespace":"default"},"spec":{"backend":{"serviceName":"mobile-gateway-service","servicePort":80}}}Events:  <none>hello ➤

With a simple LoadBalancer service, an IP address is given. The problem is only with the ingress resource.

askedJul 7, 2018 at 14:03
Tim Blackwell's user avatar
5
  • I have followed the examplecloud.google.com/kubernetes-engine/docs/tutorials/http-balancer line for line and again I have an ingress without address and stuck in stateCreating ingressCommentedJul 7, 2018 at 19:16
  • Can you please runkubectl describe ingess NAME? The events section of this output may show an issue like you hit your Backends or IP Addresses quota.CommentedJul 8, 2018 at 0:02
  • It's very strange that ingress description doesn't give you any events. Even when you describe it after like 5 minutes there are no events?CommentedJul 8, 2018 at 13:58
  • @AhmetAlpBalkan Added output from describe, unfortunately no events.CommentedJul 9, 2018 at 7:52
  • @suren This ingress has been "Creating" all weekend and still no events :(CommentedJul 9, 2018 at 7:52

3 Answers3

10

The problem in this case was I had did not include the addonHttpLoadBalancing when creating the cluster!My fault but was would have been noice to have an event informing me of this mistake in the ingress resource.

Strange that when I created a new cluster to follow the tutorial cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer using default addons includingHttpLoadBalancing that I observed the same issue. Maybe I didn't wait long enough? Anyway, working now that I have included the addon.

answeredJul 9, 2018 at 18:20
Tim Blackwell's user avatar
Sign up to request clarification or add additional context in comments.

4 Comments

HttpLoadBalancing is included in the clusters by default. If you specified--enable-addons flag, then you might need to list this add-on in there as well, but if you follow the tutorial without modifying the steps, you should be getting this add-on.
I have theHttpLoadBalancing add-on enabled on my cluster but my ingress is stuck in the "Creating Ingress" state for days. Any ideas
@AhmetB-Google, I followed the tutorial after creating my cluster from the GCP dashboard, but facing the same issue
The command to usegcloud container clusters create gara-cluster --zone=europe-west1-b --addons=HttpLoadBalancing
4

To complete the accepted answer, it's worth noting that it's possible to activate the addon on an already existing cluster (from the Google console).

However, itwill restart your clusterwith downtime (in my case, it took several minutes on an almost empty cluster). Be sure that's acceptable in your case, and do tests.

answeredDec 19, 2018 at 10:03
toadjaune's user avatar

1 Comment

(This might have been a comment on the accepted answer instead.) In my case, enabling the addon only caused the control plane (master) to restart - the nodes remained up.
0

In my case, my Ingress configuration was bad! Runkubectl describe ingress and look for errors. You'll probably need to know aboutkubectl delete -f as well, which is the opposite ofkubectl apply -f (use this after you find your errors in the.yml files)

answeredApr 10, 2023 at 1:41
Dr-Bracket's user avatar

Comments

Your Answer

Sign up orlog in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

By clicking “Post Your Answer”, you agree to ourterms of service and acknowledge you have read ourprivacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.