Public/grafana-meta-monitoring-chart
2
0
Fork 0
forked from RemoteSync/grafana-meta-monitoring-chart
Code Pull Requests Activity

Merge pull request #112 from grafana/update_ingress_documentation

Browse Source 
Add docs regarding the Ingress
This commit is contained in:
Michel Hollands 2024-05-09 17:10:06 +01:00 committed by GitHub
commit b2957d90f0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
charts/meta-monitoring/values.yaml
View File

@ -45,7 +45,12 @@ grafana:
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

4
docs/installation.md
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.