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

Haproxy stats non tls #20375

Closed
mjudeikis opened this issue Jul 20, 2018 · 8 comments
Closed

Haproxy stats non tls #20375

mjudeikis opened this issue Jul 20, 2018 · 8 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/network-edge

Comments

@mjudeikis
Copy link
Contributor

I might miss this on the docs but:

Haproxy template stats endpoint is non tls:

listen stats
bind :{{if (gt .StatsPort 0)}}{{.StatsPort}}{{else}}1936{{end}}
mode http
# Health check monitoring uri.
monitor-uri /healthz

And most of our Prometheus examples expects tls:

the result is not working haproxy metrics in Prometheus out of the box.

sh-4.2$ curl -u admin:xxxxxx https://localhost:1936/metrics
curl: (35) TCP connection reset by peer

sh-4.2$ curl -u admin:xxxxxx http://localhost:1936/metrics
# HELP apiserver_audit_event_total Counter of audit events generated and sent to the audit backend.
# TYPE apiserver_audit_event_total counter
apiserver_audit_event_total 0
# HELP apiserver_client_certificate_expiration_seconds Distribution of the remaining lifetime on the certificate used to authenticate a request.
@mjudeikis
Copy link
Contributor Author

@openshift/sig-networking ptal.

@jwforres
Copy link
Member

@openshift/sig-network-edge

@pweil-
Copy link
Contributor

pweil- commented Aug 15, 2018

@thanasisk FYI

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 13, 2018
@mjudeikis
Copy link
Contributor Author

/remove-lifecycle stale

@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 15, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/network-edge
Projects
None yet
Development

No branches or pull requests

6 participants