Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upunable to expose prometheus services usign ingress #5194
Comments
This comment has been minimized.
This comment has been minimized.
|
Thanks for your report. It looks as if this is actually a question about Kubernetes and not Prometheus itself. To make your question, and all replies, easier to find, we suggest you move this over to our user mailing list, which you can also search. If you prefer more interactive help, join or our IRC channel, #prometheus on irc.freenode.net. Please be aware that our IRC channel has no logs, is not searchable, and that people might not answer quickly if they are busy or asleep. If in doubt, you should choose the mailing list. Once your questions have been answered, please add a short line pointing to relevant replies in case anyone stumbles here via a search engine in the future. |
abhiramani-iptiq commentedFeb 8, 2019
Hi
unable to expose Prometheus services using ingress.grafana works fine usign below ingress yaml file
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: monitoring-ingress
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/rewrite-target: /
spec:
tls:
secretName: ingress-tls
rules:
http:
paths:
backend:
serviceName: grafana
servicePort: 80
backend:
serviceName: prometheus-alertmanager
servicePort: 80
backend:
serviceName: prometheus-server
servicePort: 80
backend:
serviceName: prometheus-pushgateway
servicePort: 80
Proposal
Use case. Why is this important?
“Nice to have” is not a good use case. :)
Bug Report
What did you do?
What did you expect to see?
What did you see instead? Under which circumstances?
Environment
System information:
insert output of
uname -srmherePrometheus version:
insert output of
prometheus --versionhereAlertmanager version:
insert output of
alertmanager --versionhere (if relevant to the issue)Prometheus configuration file: