-
Notifications
You must be signed in to change notification settings - Fork 82
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
Custom CA not recognized by pelorus pods (grafana and prometheus) #91
Comments
This is something we'll have to fix in our helm chart, but for now the proper workaround is to:
|
This should fix the prometheus component, but since the thanos-sidecar container is added by the operator, we need to figure out how to control that |
Does the issue at the following link mean that the grafana-operator is not easily resolved? grafana/grafana-operator#190 |
@robbbbh ; did you have to do this for our prev customer? |
@kevin-anderson-redhat no, I think there are ways to make it happen with grafana, its just the oauth container that needs it, and that config gets pretty customizable. If you can try the above and give some feedback, we can try to help troubleshoot. |
@etsauer We were not able to get grafana to operate. Still getting an untrusted cert failure in the grafana-proxy container. |
Attempts to login to prometheus and grafana fail with Error Page 500 Internal Error
Logs indicate that
oauth fails with "certificate signed by unknown authority"
The text was updated successfully, but these errors were encountered: