Reference cloud provider docs

Signed-off-by: Michel Hollands <michel.hollands@gmail.com>
This commit is contained in:
Michel Hollands 2024-05-09 16:34:12 +01:00
parent caf4eda1be
commit 315b203082
2 changed files with 11 additions and 2 deletions

View File

@ -41,11 +41,16 @@ grafana:
labels: {} labels: {}
# -- Hosts configuration for the gateway ingress, passed through the `tpl` function to allow templating # -- Hosts configuration for the gateway ingress, passed through the `tpl` function to allow templating
hosts: hosts:
- host: monitoring.example.com - host: ""
paths: paths:
- path: / - path: /
# -- pathType (e.g. ImplementationSpecific, Prefix, .. etc.) might also be required by some Ingress Controllers # -- 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 configuration for the gateway ingress. Hosts passed through the `tpl` function to allow templating
#tls: #tls:
# - secretName: grafana-tls # - secretName: grafana-tls

View File

@ -191,3 +191,7 @@ For each of the dashboard files in charts/meta-monitoring/src/dashboards folder
1. JAEGER_SAMPLER_PARAM: 1 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 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.