kubernetes azure app gateway ingress controller with external and internal pathing

Question

We are trying to set up a replacement kube cluster that has a couple of micro services on it but the majority of code still lives in a cloud service. We are using the app-gateway ingress controller as our routing mechanism. Is it possible to have an app gateway ingress controller route all requests to the external (does not live in the kub cluster) resource except those paths as defined for the micoroservices? And if so, how do we go about setting it up?

this is dotnetcore for linux with helm as the orchestration.

the layout would look something like this...

• default: /* => cloud service
• microservice 1: /ms1/route1 or /ms1/route2 => internal kube deployment 1
• microservice 2: /ms2/route1 => internal kube deployment 2

Answer 1

Is it possible to have an app gateway ingress controller route all requests to the external (does not live in the kub cluster) resource except those paths as defined for the micoroservices?

I don't think it's possible to route the requests to the resources that outside the Kubernetes. You can take a look at What is Ingress :

Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource.

     internet
        |
   [ Ingress ]
   --|-----|--
   [ Services ]

I think you can route the outside requests to your microservices or your Kubernetes services through Azure Application Gateway .

Answer 2

it is possible. create a service with selectors or external service and point it to your cloud service and route requests from /* to it.

apiVersion: v1
kind: Service
metadata:
  name: name
spec:
  type: ExternalName
  externalName: url-goes-here