-
Notifications
You must be signed in to change notification settings - Fork 70
Closed
Labels
kind/questionIndicates an issue that is a support question.Indicates an issue that is a support question.
Description
What happened:
I1028 08:22:39.983799 1 handler.go:275] Adding GroupVersion work.karmada.io v1alpha1 to ResourceManager
I1028 08:22:39.983836 1 handler.go:275] Adding GroupVersion work.karmada.io v1alpha2 to ResourceManager
I1028 08:22:40.181451 1 handler.go:275] Adding GroupVersion work.karmada.io v1alpha1 to ResourceManager
I1028 08:22:40.181495 1 handler.go:275] Adding GroupVersion work.karmada.io v1alpha2 to ResourceManager
I1028 08:22:40.348449 1 handler.go:275] Adding GroupVersion work.karmada.io v1alpha1 to ResourceManager
I1028 08:22:40.795437 1 handler.go:275] Adding GroupVersion cluster.karmada.io v1alpha1 to ResourceManager
I1028 08:22:40.856143 1 handler.go:275] Adding GroupVersion cluster.karmada.io v1alpha1 to ResourceManager
I1028 08:22:48.519969 1 controller.go:624] quota admission added evaluator for: serviceaccounts
E1028 09:20:55.015580 1 authentication.go:73] "Unable to authenticate the request" err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
E1028 09:21:29.889828 1 authentication.go:73] "Unable to authenticate the request" err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
E1028 09:22:04.774205 1 authentication.go:73] "Unable to authenticate the request" err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
E1028 09:23:14.509123 1 authentication.go:73] "Unable to authenticate the request" err="[invalid bearer token, square/go-jose: error in cryptographic primitive]"
root@node1:~/dashboard# kubectl describe serviceaccount karmada-dashboard -n karmada-system
Name: karmada-dashboard
Namespace: karmada-system
Labels: addonmanager.kubernetes.io/mode=Reconcile
kubernetes.io/cluster-service=true
Annotations: <none>
Image pull secrets: <none>
Mountable secrets: <none>
Tokens: karmada-dashboard-secret
Events: <none>
root@node1:~/dashboard# kubectl get -n karmada-system secret karmada-dashboard-secret -o jsonpath="{.data.token}" | base64 --decode
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
root@iZj6c90gahowqyaz95yncqZ:~/dashboard# kubectl version
Client Version: v1.31.2
Kustomize Version: v5.4.2
Server Version: v1.31.0
- Karmada version: v1.11.1
- Karmada Dashboard version: latest
- Others:
Metadata
Metadata
Assignees
Labels
kind/questionIndicates an issue that is a support question.Indicates an issue that is a support question.