E0222 18:06:34.828465 1 authentication.go:63] “Unable to authenticate the request” err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
E0222 18:06:34.881516 1 authentication.go:63] “Unable to authenticate the request” err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
E0222 18:06:34.883677 1 authentication.go:63] “Unable to authenticate the request” err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
E0222 18:06:35.828284 1 authentication.go:63] “Unable to authenticate the request” err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
E0222 18:06:35.830990 1 authentication.go:63] “Unable to authenticate the request” err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
E0222 18:06:35.884048 1 authentication.go:63] “Unable to authenticate the request” err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
E0222 18:06:35.886549 1 authentication.go:63] “Unable to authenticate the request” err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
The log of my k8s test cluster (api server logs) fills up with those messages.
It’s not a production cluster - but I ask myself how to find out what is causing those messages.
If I disconnect the network interface of the master node, the messages stop.
If I disconnect the network interface of every node (1 at a time), the messages continue.
Is there some kind of debug logging to see more details about the invalid bearer token and where the request comes from?
Additional Infos:
Kubernetes version: 1.23.3
Cloud being used: bare metal (api server not reachable from internet)
Installation method: kubeadm
Host OS: ubuntu server 20.04
CNI and version: weave 2.8.1
CRI and version: contained 1.19
1 x Master Node (Kube API Server)
4 x Worker Node