prometheus-k8s route is returning 404 after OKD cluster upgrade to 4.13 #1698
Replies: 3 comments 6 replies
-
|
Please attach (or upload to the public file sharing service) must-gather archive |
Beta Was this translation helpful? Give feedback.
-
|
If you're referring to the Prometheus UI, it is not accessible by default anymore since a few versions. See #1420 (comment). |
Beta Was this translation helpful? Give feedback.
-
|
Hi, this is not to be considered a bug. Although uncomfortable, the UI has been deprecated in 4.10 as reported in the 4.10 ocp release notes:
Also, 4.12 OCP reports the removal in [1] and [2]. Depending on your use case, you might expose the thanos-querier UI via temporary solutions like |
Beta Was this translation helpful? Give feedback.
-
|
@aleskandro Thank You for the info! I tried port-forwarding but it does the redirection towards openshift login, as the oauth provider is openshift. |
Beta Was this translation helpful? Give feedback.
-
|
you should do the redirection on port 9090 (and you will not be "oauth-proxied"). |
Beta Was this translation helpful? Give feedback.
-
|
this works (bypassing authentication): oc port-forward -n openshift-monitoring deployment/thanos-querier 9090Alternatively, I used this hack to access the thanos UI and get oauth working as before (users bound to the cluster-monitoring-view role will be able to access it). It is not thoroughly tested and shouldn't be considered secure. After deploying the manifest, you should get a route at |
Beta Was this translation helpful? Give feedback.
-
|
@aleskandro Thank You :) |
Beta Was this translation helpful? Give feedback.
-
After the cluster upgrade, the prometheus version is changed to "app.kubernetes.io/version=2.42.0" and the route is returning "404 page not found".
It was working in version "app.kubernetes.io/version=2.32.1"
Describe the bug
Version
How reproducible
Launch the prometheus route
Log bundle
Beta Was this translation helpful? Give feedback.
All reactions