easylinux/kube-prometheus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #200 from lanmarti/patch-1

Browse Source 
#199 Clarify externalUrl difference for Grafana
This commit is contained in:
Frederic Branczyk
2019-08-29 16:48:02 +02:00
committed by GitHub
parent ea6c1195a6 3eda46c36c
commit 5310aef112
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/exposing-prometheus-alertmanager-grafana-ingress.md
View File

@@ -81,7 +81,7 @@ k.core.v1.list.new([
]) ])
``` ```
In order to expose Alertmanager and Grafana, simply create additional fields containing an ingress object, but simply pointing at the `alertmanager` or `grafana` instead of the `prometheus-k8s` Service. Make sure to also use the correct port respectively, for Alertmanager it is also `web`, for Grafana it is `http`. Be sure to also specify the appropriate external URL. In order to expose Alertmanager and Grafana, simply create additional fields containing an ingress object, but simply pointing at the `alertmanager` or `grafana` instead of the `prometheus-k8s` Service. Make sure to also use the correct port respectively, for Alertmanager it is also `web`, for Grafana it is `http`. Be sure to also specify the appropriate external URL. Note that the external URL for grafana is set in a different way than the external URL for Prometheus or Alertmanager. See [ingress.jsonnet](../examples/ingress.jsonnet) for how to set the Grafana external URL.
In order to render the ingress objects similar to the other objects use as demonstrated in the [main readme](../README.md#usage): In order to render the ingress objects similar to the other objects use as demonstrated in the [main readme](../README.md#usage):