Replies: 5 comments 7 replies
-
Does it also fail using other kubeconfigs in this dir? |
Beta Was this translation helpful? Give feedback.
-
Yes, it fails with the other kubeconfigs as well. For the locahost.kubeconfig I get an Unauthorized message:
Here's with loglevel set to 10:
I also noticed the oc client on the nodes is old, I would have thought it get's updated with cluster updates but I guess not. Is it fine to replace the oc binary on them? |
Beta Was this translation helpful? Give feedback.
-
I tried with an updated oc binary as well but same result:
|
Beta Was this translation helpful? Give feedback.
-
Hi, I am having the exact same issue, did you manage to solve it? |
Beta Was this translation helpful? Give feedback.
-
Hi regard power on openshift cluster v4.10 after more then 90 days it was off. |
Beta Was this translation helpful? Give feedback.
-
Our OKD 4.10 cluster was shutdown for a few months while testing a trial version of openshift, however after starting it back up we couldn't log in through the oc client. We noticed that oc get csr shows several certs in a pending state:
We tried following the procedure documented here: https://docs.okd.io/4.10/backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-3-expired-certs.html
However when trying to approve the certificate we get a Forbidden error:
The only kubeconfig that will even work with oc get csr is /etc/kubernetes/kubeconfig, using /etc/kubernetes/static-pod-resources/kube-apiserver-certs/secrets/node-kubeconfigs/lb-int.kubeconfig (mentioned here - https://access.redhat.com/solutions/5953441) doesn't work, we get "error: You must be logged in to the server (Unauthorized)". We tried the other kubeconfig files as well without any luck.
OS Version:
Any ideas on getting these certificates approved?
Beta Was this translation helpful? Give feedback.
All reactions