Ingress - How to properly route to two services with https

General Discussions
1

I’m trying to deploy a ReactJs app and an Express-GraphQL server through Kubernetes. But I’m having trouble setting up an ingress to route traffic to both services. Specifically I can no longer reach my back-end.

When I made the React front-end and Express back-end as separate services and exposed them, it ran fine. But now I’m trying to enable HTTPS and DNS. And route to both of them through Ingress.

Here are my service yaml files

apiVersion: v1
kind: Service
metadata:
  name: bpmclient
  namespace: default
spec:
  ports:
  - port: 80
    protocol: TCP
    targetPort: 5000
  selector:
    run: bpmclient
  type: NodePort

apiVersion: v1
kind: Service
metadata:
  name: bpmserver
  namespace: default
spec:
  ports:
  - port: 3090
    protocol: TCP
    targetPort: 3090
  selector:
    run: bpmserver
  type: NodePort

and my Ingress…

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: bpm-nginx
  annotations:
    kubernetes.io/ingress.global-static-ip-name: bpm-ip
    networking.gke.io/managed-certificates: bpmclient-cert
    ingress.kubernetes.io/enable-cors: "true"
    ingress.kubernetes.io/cors-allow-origin: "https://example.com"
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  rules:
  - host: example.com
    http:
      paths:
      - path: /v2/*
        backend:
          serviceName: bpmserver
          servicePort: 3090
      - path: /*
        backend:
          serviceName: bpmclient
          servicePort: 80

Through this setup I’ve been able to visit the client successfully using https. But I can’t reach my back-end anymore through the client or just browsing to it. I’m getting a 502 server error. But I check the logs for the back-end pod and don’t see anything besides 404 logs.

My front-end is reaching the back-end through example.com/v2/graphql. When I run it locally on my machine I go to localhost:3090/graphql. So I don’t see why I’m getting a 404 if the routing is done correctly.

2

Is the bpm server expecting / for the client to hit? I’d check around there.