-
Notifications
You must be signed in to change notification settings - Fork 589
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
RedPanda Public metrics #23661
Comments
Hello @maksym-iv - I am sorry to hear that the stats disappeared! This change happened in #21372 and is indeed controlled by a cluster property Link to docs on how to change cluster properties: https://docs.redpanda.com/current/manage/kubernetes/k-cluster-property-configuration/ |
Also, we should also be supporting TLS 1.2 by default, if that's not the case than thats a larger bug. |
Hi @maksym-iv, sorry again you're experiencing issues. Would it be possible for you to send me the output of the Also feel free to DM me (@MichaelBoquard) on the Redpanda community slack channel. |
Sure, here is the output, I've also added tls_min_version v1.2
TLSv1.2 openssl/curl:
TLSv1.3 openssl/curl:
tls_min_version v1.0Set via
TLSv1.2 openssl/curl:
TLSv1.3 openssl/curl:
|
Version & Environment
Redpanda version:
v24.2.5
Helm: v24.2.5
Platform: K8s (GKE)
What went wrong?
We are using RedPanda for quite a while, and started the upgrade from
v24.1.7
(helm5.8.8
) tov24.2.5
(helm5.9.5
).Everything works fine, except the
/public_metrics
. We are using TLS, and apparently Admin API (from where metrics is served) switched to TLSv1.3 only, and this is a good thing for sure. However, all metrics disappeared from Google Monitoring (prometheus).Since we are running on the GKE we are using GMP (Google Managed Service for Prometheus), and it looks like there is an issue in the GMP that prevents scraping TLSv1.3 only endpoints. Although in their docs it is stated that TLS13 can be used, in reality there is an error.
And I've tried to use the good old
openssl s_client -connect 10.0.24.158:9644 -tls1_3/-tls1_2
to confirm it's TLS1.3, also tried local prometheus targeting endpoints in GKE with TLS13 set in the scrape config, all works.So meanwhile GCP is registering the issue, I wonder, is there a way to launch Admin API with TLS1.2 support? Tried
tls_min_version
, but that didn't work for the Admin API.What should have happened instead?
How to reproduce the issue?
v24.2.5
in the GCPv0.12.1
, imagegke.gcr.io/prometheus-engine/prometheus:v2.45.3-gmp.7-gke.0@sha256:8c8e35af7e2b92ac9d82ce640621c0d3aa10d7d62856681af3572d0a8fbb787b
PodMonitoring
statusJust to note, I don't believe it's the RedPanda issue, it's GMP fails to scrape, I just wonder if there is a way to have TLS1.2 within admin API and RedPanda
v24.2.5
The text was updated successfully, but these errors were encountered: