Cannot reach resource through ingress on GKE

Question 1

I'm trying to create an Ingress resource that fans out to two services that are running healthily. This is my very simple config:

apiVersion: extensions/v1beta1kind: Ingressmetadata:  name: my-ingress  namespace: defaultspec:  rules:    - http:        paths:          - path: /*            backend:              serviceName: service1              servicePort: 8080          - path: /service2/*            backend:              serviceName: service2              servicePort: 9090

Only requests to the root (/) path seem to work. I've been trying to trouble shoot this using similar posts online, but nothing has worked for me.

What can I do?

Edit:

This config works fine on Minikube, but doesn't on GKE?

Question 2

What do you get onservice2? 404?

Question 3

Yes, I get a404 onservice2.

Question 4

Do you have actually anything serving on path/service2 of your backend?

Question 5

404 implies the request is reaching the backend, there is just nothing there. If you check the logs on one of the backends for service2, you should see the requests come in along with the error and that should help you debug this further

Question 6

If you're using the default ingress controller of GKE, then theyaml looks good to me. I will suggest you, to recheck the services (i.e. service1, service2) ofNodePort type and make sure that they are working fine.

In case you're using theNGINX Ingress Controller of the version above or equal tonginx-0.20.0, you need to set thenginx.ingress.kubernetes.io/use-regex annotation totrue (the default isfalse) toenable the case sensitive regular expression.

Just like:

apiVersion: extensions/v1beta1kind: Ingressmetadata:  name: my-ingress  namespace: default  annotations:    nginx.ingress.kubernetes.io/use-regex: "true"spec:  rules:    - http:        paths:          - path: /*            backend:              serviceName: service1              servicePort: 8080          - path: /service2/*            backend:              serviceName: service2              servicePort: 9090

Question 7

Thank you! This seems to work on Minikube, but I'm still having issues on GKE. By changing my services to kindNodePort fromLoadBalancer, I can now access the resources on my Minikube cluster. However, I am now gettingdefault backend - 404 when trying to accessservice2 through my GKE cluster.

Question 8

I have a working configuration on Azure, it's very simple yet differs from yours in a few ways. I rewrote your yaml accordingly, see if that helps:

apiVersion: extensions/v1beta1kind: Ingressmetadata:  name: my-ingress  namespace: default  annotations:    kubernetes.io/ingress.class: nginx    nginx.ingress.kubernetes.io/rewrite-target: /$1spec:  rules:    - http:        paths:          - path: /service2/?(.*)            backend:              serviceName: service2              servicePort: 9090          - path: /?(.*)            backend:              serviceName: service1              servicePort: 8080

The notable differences are:

Paths are flipped so that the more specific one is higher up. Not sure if that has any influence.
Changed the simple wildcard to a look-ahead:* =>?(.*). This allows me to use thenginx.ingress.kubernetes.io/rewrite-target annotation to make sure that I don't lose the part of the url that follows/service2/. So if you were calling anythingbut /service2/ exactly, this might help.

Question 9

Interesting. This works exactly as my config does on Minikube, but on GKE I get this error: ``` Error during sync: error running load balancer syncing routine: loadbalancer default-my-ingress--cbc24f100656b420 does not exist: CreateUrlMap: googleapi: Error 400: Invalid value for field 'resource': '{ "name": "k8s-um-default-my-ingress--cbc24f100656b420", "hostRule": [{ "host": ["*"], ...'. Invalid path pattern, invalid ```

Question 10

Have you tried addingnginx.ingress.kubernetes.io/use-regex: "true" tothis configuration, as suggested before?

Question 11

If you are usingnginx, please check-out thisgithub issue.

If you are usingtraefik try:

apiVersion: networking.k8s.io/v1beta1kind: Ingressmetadata:  annotations:    kubernetes.io/ingress.class: traefik  name: my-ingressspec:  rules:  - http:      paths:      - path: /        backend:          serviceName: service1      - path: /service2/        backend:          serviceName: service2

Kamol Hasan 13.9k2 gold badges45 silver badges52 bronze badges · Accepted Answer · 2019-12-21 23:39:02Z

If you're using the default ingress controller of GKE, then theyaml looks good to me. I will suggest you, to recheck the services (i.e. service1, service2) ofNodePort type and make sure that they are working fine.

In case you're using theNGINX Ingress Controller of the version above or equal tonginx-0.20.0, you need to set thenginx.ingress.kubernetes.io/use-regex annotation totrue (the default isfalse) toenable the case sensitive regular expression.

Just like:

apiVersion: extensions/v1beta1kind: Ingressmetadata:  name: my-ingress  namespace: default  annotations:    nginx.ingress.kubernetes.io/use-regex: "true"spec:  rules:    - http:        paths:          - path: /*            backend:              serviceName: service1              servicePort: 8080          - path: /service2/*            backend:              serviceName: service2              servicePort: 9090

Thank you! This seems to work on Minikube, but I'm still having issues on GKE. By changing my services to kindNodePort fromLoadBalancer, I can now access the resources on my Minikube cluster. However, I am now gettingdefault backend - 404 when trying to accessservice2 through my GKE cluster.

Movatterモバイル変換

Collectives™ on Stack Overflow

Cannot reach resource through ingress on GKE

Edit:

3 Answers3

1 Comment

2 Comments

Comments

Your Answer

Sign up orlog in

Post as a guest

Related

Hot Network Questions

Subscribe to RSS