Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to expose prometheus services usign ingress #5194

Closed
abhiramani-iptiq opened this Issue Feb 8, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@abhiramani-iptiq
Copy link

abhiramani-iptiq commented Feb 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:

  • hosts:
    • mydomain.com
      secretName: ingress-tls
      rules:
  • host: mydomain.com
    http:
    paths:
    • path: /grafana
      backend:
      serviceName: grafana
      servicePort: 80
    • path: /alertmanager
      backend:
      serviceName: prometheus-alertmanager
      servicePort: 80
    • path: /prometheus
      backend:
      serviceName: prometheus-server
      servicePort: 80
    • path: /pushgateway
      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 -srm here

  • Prometheus version:

    insert output of prometheus --version here

  • Alertmanager version:

    insert output of alertmanager --version here (if relevant to the issue)

  • Prometheus configuration file:

insert configuration here
  • Alertmanager configuration file:
insert configuration here (if relevant to the issue)
  • Logs:
insert Prometheus and Alertmanager logs relevant to the issue here
@simonpasquier

This comment has been minimized.

Copy link
Member

simonpasquier commented Feb 8, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.