Microcks UI is not loading on behind Azure application gateway Ingress

I tried to deploy Microcks on AKS along with application gateway as an Ingress. I could see all the pods are running and ingress is route the microcks requests to host.

Below are the log outputs, POD status NAME READY STATUS RESTARTS AGE microcks-5f6d6dc94b-9p95p 1/1 Running 0 18d microcks-keycloak-69985858b9-vg82r 1/1 Running 3 18d microcks-keycloak-postgresql-bd87d8fc7-pz8sq 1/1 Running 0 18d microcks-mongodb-59f64665c4-fctk5 1/1 Running 0 17d microcks-postman-runtime-5bf9944956-wm4lr 1/1 Running 0 18d

Ingress microcks Annotations Name: microcks Namespace: XXX Address: X.X.X.X Default backend: default-http-backend:80 Rules: Host Path Backends XXX.org /microcks/* microcks:8080 (172.16.1.126:8080) Annotations: appgw.ingress.kubernetes.io/appgw-ssl-certificate: default appgw.ingress.kubernetes.io/backend-path-prefix: / appgw.ingress.kubernetes.io/request-timeout: 120 appgw.ingress.kubernetes.io/ssl-redirect: true kubernetes.io/ingress.class: azure/application-gateway meta.helm.sh/release-name: microcks meta.helm.sh/release-namespace: XXX Events: <none>

In the depth dive, I came to know that the URL is redirection is not happening . Meaning, the context path for Microcks need to be set to run the microcks behind the reverse proxy.

When hit the URL https://xxx.org/microcks/ and getting below exceptions.

Loading failed for the <script> with source “https://XXX.org/main.3bf80884829c016c441a.js”. microcks:15:1
Loading failed for the <script> with source “https://XXX.org/runtime.0b05ef57c964121efcc0.js”.

**Microcks path is missing in URL** 
URL suppose to be  https://XXX.org/microcks/runtime.0b05ef57c964121efcc0.js
but getting URL is https://XXX.org/runtime.0b05ef57c964121efcc0.js  (Microcks is missing)
Looks context path is taken correctly to load the JS & CSS.

Can anyone help me with more lights how to context path on Microcks application? Seeking for support, please advise.

[meyyazhagan]

Thanks for the note, @devcovato I have overcome the issue by configuring the domain based routing in AppGw ingress instead of path based routing, which will have dedicated endpoint. Below are the snippet for ingress deployment. And, it works well.

kind: Ingress
metadata:
  name: go-server-ingress-certificate
  namespace: test-ag
  annotations:
    kubernetes.io/ingress.class: azure/application-gateway
    appgw.ingress.kubernetes.io/appgw-ssl-certificate: "name-of-appgw-installed-certificate"
spec:
  rules:
  - host: www.contoso.com
    http:
      paths:
      - backend:
          serviceName: websocket-repeater
          servicePort: 80

[lbroudoux]

Thanks all for sharing these configuration details. Happy to know it’s working well!