istio: Grafana and Prometheus UIs do not work with non-root contextpath

I had the same issue and was able to solve it by creating a virtualservice with prefix and by setting two env vars in the grafana deployment template (trailing slash is needed):

          - name: GF_SERVER_ROOT_URL
            value: %(protocol)s://%(domain)s/grafana/
          - name: GF_SERVER_DOMAIN
            value: example.org

I suggest adding something like this to the Grafana deployment template:

{{- range $key, $value := .Values.env }}
          - name: "{{ $key }}"
            value: "{{ $value }}"
{{- end }} 

and in the Grafana values.yaml: env: {} updated 08/08/19: Istio virtualservice:

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: "istio-dashboard-app"
spec:
  hosts:
    - "mydomain.com"
  gateways:
    - default-gateway
  http:
    - match:
      - uri:
          prefix: "/grafana/"
      rewrite:
        uri: /
      route:
        - destination:
            host: grafana.istio-system.svc.cluster.local
            port:
              number: 3000

Grafana is highly customizable via env vars and this allows adding any desired amount of them. I can open a PR if necessary.

@arjav-desai @mklettner try this virtualservice match rule:

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: "istio-dashboard-app"
spec:
  hosts:
    - "mydomain.com"
  gateways:
    - default-gateway
  http:
    - match:
      - uri:
        prefix: /grafana/
      - uri:
        prefix: /grafana
      rewrite:
        uri: /
      route:
        - destination:
            host: grafana.istio-system.svc.cluster.local
            port:
              number: 3000

adding two uri match rule with and without trailing slash works fine on my env.

@rafik8 I can’t assign you. You aren’t a choice – this happens with new people. I assigned myself but you can do the work and submit the PR, which I will mark as ok-to-test.