-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generate bearer token failed #38
Comments
The Karmada dashboard project is still far from being available, and the development of this project has actually stagnated due to the lack of front-end developers. We are also seeking developers who are willing to contribute to this project. |
same problems |
TLDR: export KUBECONFIG=path/to/karmada-kubeconfig
kubectl -n karmada-system create token karmada-dashboard if you want a long lived token, you can following next steps kubectl apply -f - <<EOF
apiVersion: v1
kind: Secret
metadata:
name: karmada-dashboard-secret
namespace: karmada-system
annotations:
kubernetes.io/service-account.name: karmada-dashboard
type: kubernetes.io/service-account-token
EOF
kubectl -n karmada-system get secret/karmada-dashboard-secret -ojsonpath='{.data.token}' | base64 -d && echo It's not the problem of karmada. It's KEP-1205 which introduce the feature that caused not automatic generated token for serviceaccount. |
If there is any plan to maintain karma-dashboard, may be i can do it part time 🤣 |
Glad to hear that and thank you! |
I'll attend the meeting on time 😄 |
I installed Karmada by Karmada command-line tool on my own cluster (karmadactl init) and joined cluster with name member 2 to Karmada.
Then I tried to install Karmada Dashboard by following the steps on github and I found out that I only had karmada-apiserver.config file (seems like I am missing something about karmada-host). Also, when I generated bearer token, it showed this error.
The text was updated successfully, but these errors were encountered: