Expose a kubernetes deployment (frontend) using ingress controller

Question

I am deploying a number of docker containers of micro-services and angular frontend on Kubernetes. I have exposed the services using an ingress controller specifying each service using this, and specifying paths in backend.

apiVersion: extensions/v1beta1
kind: Ingress

For my frontend, I have created a service with type loadbalancer.

apiVersion: v1
kind: Service
metadata:
  annotations:
    service.beta.kubernetes.io/azure-load-balancer-resource-group: my-resource-group
  name: myapp-svc
  namespace: ui
spec:
  loadBalancerIP: SOME_IP_ADDRESS
  type: LoadBalancer
  ports:
  - port: 80
 selector:
   app: myapp

This works fine but now I have two IP addresses, one for the UI loadbalancer, and other of the ingress controller (for APIs).

Can I do this with just one IP address?

How can I expose the UI using ingress controller itself without creating external loadbalancer?

Answer 1

Try this way -

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/rewrite-target: /$1
    nginx.ingress.kubernetes.io/service-upstream: "true"
  name: rule-name
  namespace: default
spec:
  rules:
  - host: hostname
    http:
      paths:
      - backend:
          serviceName: frontend-service
          servicePort: port-number
        path: /(.*)
      - backend:
          serviceName: backend-service
          servicePort: port-number
        path: /api/(.*)

---

You can use the above defined strategy where you can directly map front end at / and use rewrite-target to map anything like hostname/api to backend service.

You can keep frontend and backend services at clusterIP level only