diff --git a/charts/meta-monitoring/values.yaml b/charts/meta-monitoring/values.yaml
index ca5f6e5..719dd0d 100644
--- a/charts/meta-monitoring/values.yaml
+++ b/charts/meta-monitoring/values.yaml
@@ -41,11 +41,16 @@ grafana:
     labels: {}
     # -- Hosts configuration for the gateway ingress, passed through the `tpl` function to allow templating
     hosts:
-      - host: monitoring.example.com
+      - host: ""
         paths:
           - path: /
             # -- pathType (e.g. ImplementationSpecific, Prefix, .. etc.) might also be required by some Ingress Controllers
-            # pathType: Prefix
+            pathType: Prefix
+            # backend:
+            #   service:
+            #     name: TODO
+            #     port:
+            #       number: TODO
     # -- TLS configuration for the gateway ingress. Hosts passed through the `tpl` function to allow templating
     #tls:
     #  - secretName: grafana-tls
diff --git a/docs/installation.md b/docs/installation.md
index c49b2b1..b2d70f0 100644
--- a/docs/installation.md
+++ b/docs/installation.md
@@ -191,3 +191,7 @@ For each of the dashboard files in charts/meta-monitoring/src/dashboards folder
    1. JAEGER_SAMPLER_PARAM: 1
 
 1. If Loki is installed in a different namespace you can create an [ExternalName service](https://kubernetes.io/docs/concepts/services-networking/service/#externalname) in Kubernetes to point to the mmc-alloy service in the meta monitoring namespace
+
+## Configure external access using an Ingress in local mode
+
+When using local mode by default a Kubernetes [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) object is created to access the Grafana instance. This will need to be adapted to your cloud provider by updating the `grafana.ingress` section of the `values.yaml` file provided to Helm. Check the documentation of your cloud provider for available options.
\ No newline at end of file