You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
It seems in our environment (where we pass in TLS certs to our Grafana service so that it's encrypted end to end) that the Grafana Operator stopped being able to connect with our Grafana instances after #1628 was shipped in 5.13.0. We get the following reconciliation errors:
"status": {
"hash": "9250f003846c19a973bd035ce560da23aaad2fdc855a951d63c99d75b7c40a03",
"lastMessage": "fetching data sources: Get \"https://grafana-app-service.grafana:3000/api/datasources\": tls: failed to verify certificate: x509: certificate signed by unknown authority",
"lastResync": "2024-09-12T17:50:18Z",
"uid": "loki"
}
Thanks for reporting this. The TLS settings introduced in #1628 should have only affected external instances, but it had the unintended side effect of requiring complete certificate chains on all instances.
As a workaround, you can try mounting your ca.crt in the operator manager container under /etc/ssl/certs/ca-certificates.crt until we have a fix ready.
theSuess
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Sep 17, 2024
Describe the bug
It seems in our environment (where we pass in TLS certs to our Grafana service so that it's encrypted end to end) that the Grafana Operator stopped being able to connect with our Grafana instances after #1628 was shipped in 5.13.0. We get the following reconciliation errors:
Logs:
Version
v5.13.0
To Reproduce
Create a Grafana with a TLS config...
The text was updated successfully, but these errors were encountered: