Open KSPlatform opened 2 years ago
Thanks for reporting. That is weird. The Prometheus API client used by Pyrra didn't change between releases. What happens if you rollback to v0.4.4? Does it work with the same configuration still?
Yes it works when I get back to v0.4.4. Somehow same configuration.. What I have/don't have extra in the config is:
Thanks
Did you have any updates? It's sadly super hard to judge remotely.
Tried with a fresh system on OpenShift v4.10, same case. Used directly v0.5.0 image. Error in those columns.. Looked for any debug parameters, but couldn't find one.. Please redirect me for debugging the issue..
Hi, Would be great if direct me for debugging..Somehow stuck for migration to newer versions.. Thanks
I'm sadly not sure how to help you further. I don't have access to an OpenShift cluster. If you could dig some more and post findings that might be helpful to get to the bottom of this. Sorry.
Hi, I'm trying Pyrra for the first time. I also have OpenShift 4.10 and I'm facing this same issue
I wish I had such easy access to an OpenShift cluster compared to back when working at Red Hat on OpenShift. Sadly this isn't the case right now. If you could help by providing more information that'd be fantastic.
Someone was very kind and I finally had access to OpenShift 4.12. Sadly I couldn't get it working until I had to leave again. It looks like Pyrra v0.4 didn't work and v0.5 doesn't either. I could reproduce this.
It's definitely an authorization issue. I'm a bit rusty on what exactly needed to be done for OpenShift, so help is appreciated.
The service-ca can be read from the mounted ConfigMap volume and I don't think we do anything with it.
https://github.com/pyrra-dev/pyrra/blob/e88234910527fe08f125f718319d1e9b93463ec5/main.go#L105-L109
+ TLSConfig: promconfig.TLSConfig{
+ CAFile: "/etc/ssl/certs/service-ca.crt",
+ },
It might be that we need to send Authorization Bearer tokens along with each request? Even if that's the case, do we need to tell the Prometheus to accept incoming requests from Pyrra?
Side note: It probably makes more sense to query Thanos queriers on latest OpenShift versions?
We are sending the bearer token, as mounted https://github.com/pyrra-dev/pyrra/blob/e88234910527fe08f125f718319d1e9b93463ec5/examples/openshift/deploy/api.yaml#L32
unless the syntax in pyrra changed, that should be the same still.
are you following the examples from here ?
I have exactly the same problem. Pyrra v0.4.4 is working fine but if I upgrade to v0.5.0 then UI shows the same errors. I am using OpenShift 4.12. Note: I am following the example here. I am connecting to the Thanos queriers.
Hi, An addition to inform Alert manager, Thanos Querier and Thanos Ruler "web" access is removed and the data can only be accessed by command line or via OCP console after v4.10(https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.html?extIdCarryOver=true&intcmp=7013a000002CtetAAC&sc_cid=7013a0000034hRXAAY#ocp-4-10-third-party-monitoring-component-uis-removal). So, not sure Prometheus links in Pyrra are useful .. Things are getting harder for OCP side..
Hi, Just used the new image as seems the only change for OpenShift is the image version in the yaml files. I see the new latency column. But availability and error budget columns are all "Error". I see client error 403 in api logs:
API logs
Kubernetes pod logs:
All service accounts and cluster role bindings are in place. Am i missing a point for the new version? Thanks