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

Helm chart metrics broken? #145

Closed
dhess opened this issue Jan 7, 2025 · 4 comments · Fixed by #147
Closed

Helm chart metrics broken? #145

dhess opened this issue Jan 7, 2025 · 4 comments · Fixed by #147

Comments

@dhess
Copy link

dhess commented Jan 7, 2025

Hi, thanks for this very useful project.

Some of the changes in #133 seem to be related to making metrics more secure. I believe the Helm chart needs to be updated to support the new configuration options, because since deploying v0.7.0, our metrics are now broken:

cloudflare-zero-trust-operator 2025/01/07 23:23:28 http: TLS handshake error from 127.0.0.1:47230: client sent an HTTP request to an HTTPS server

We use a ServiceMonitor similar to the one you've defined here: https://github.com/BojanZelic/cloudflare-zero-trust-operator/blob/main/config/prometheus/monitor.yaml

It has worked fine up until the v0.7.0 upgrade, and now repeatedly gives the error message shown above. I assume that either --metrics-secure=false needs to be set, or port 8443 needs to be used for metrics and the kube-rbac-proxy config changed to match.

@BojanZelic
Copy link
Owner

This should be fixed by #147

we removed the kube-rbac-proxy component since it's not needed anymore; metrics scraping should happen over 8443

Helm chart v0.7.1 should have the fix

@dhess
Copy link
Author

dhess commented Jan 11, 2025

Thanks! Can you publish the new Helm chart, please?

@BojanZelic
Copy link
Owner

There's a new chart published https://github.com/zelic-io/charts/releases/tag/cloudflare-zero-trust-operator-0.7.1

@dhess
Copy link
Author

dhess commented Jan 13, 2025

Confirmed fixed, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants