Unable to authenticate the request. Invalid bearer token, service account token has expired. #11011
Unanswered
TheOnlyWei
asked this question in
Q&A
Replies: 1 comment
-
It's most likely a process running pod that for some reason hasn't reloaded its service account credentials. You can try deleting pods until it goes away, or you could enable apiserver audit logging and identify the denied requests from those. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm getting the errors below filling up the K3s.service logs (
sudo journalctl --unit=k3s.service -n 100 --no-pager
), and I'm wondering what that is caused by and how to resolve it. They seem to be inconsequential to user workloads, but these logs are spammed every few seconds and clutter the logs.I have done a series of service account signing key rotations using the
k3s certificate rotate-ca
on the cluster. I have also configuredservice-account-max-token-expiration
to1h00m0s
forkube-apiserver-arg
:We only have one pod in the
kube-system
namespace, but we do have other pods in other name spaces.Beta Was this translation helpful? Give feedback.
All reactions