kubelet metrics not working in after upgrade to OKD 4.13 about cluster-monitoring-operator HOT 12 CLOSED

The error message says 401 - Unauthorized, so this would point to a certificate issue/ . Maybe prometheus is trying to use invalid client certificates?

Did you update straight from 4.11 to 4.13? We don't generally support upgrades that skip a version, similar to okd in general.

from cluster-monitoring-operator.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from cluster-monitoring-operator.

update straight from 4.11 to 4.13?

No，but I encountered the same problem

from cluster-monitoring-operator.

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

from cluster-monitoring-operator.

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

from cluster-monitoring-operator.

@openshift-bot: Closing this issue.

from cluster-monitoring-operator.

We have the same issue with OKD 4.14 - are there any workarounds for this?

/reopen

from cluster-monitoring-operator.

@outofrange: You can't reopen an issue/PR unless you authored it or you are a collaborator.

from cluster-monitoring-operator.

reopening as this is still an issue and obviously is affecting others as well

/reopen

from cluster-monitoring-operator.

We use mTLS to secure the metrics scraping. As indicated in my earlier comment a 401 error points to an issue with these certificates. Possibly the certs have been rotated and Prometheus is not aware. Does a restart of the Prometheus pods perhaps fix this?

from cluster-monitoring-operator.

We use mTLS to secure the metrics scraping. As indicated in my earlier comment a 401 error points to an issue with these certificates. Possibly the certs have been rotated and Prometheus is not aware. Does a restart of the Prometheus pods perhaps fix this?

I have tried that :) didn't work

from cluster-monitoring-operator.

Same here - deleted the secret metrics-clients-certs (I think it's called) a couple of times and restarted CMO (and prometheus and basically everything else) to force rotated certificates, but didn't help.

from cluster-monitoring-operator.