Skip to content
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

deploy karmada in kind dashboard init failed #142

Closed
JamesBonddu opened this issue Oct 27, 2024 · 7 comments
Closed

deploy karmada in kind dashboard init failed #142

JamesBonddu opened this issue Oct 27, 2024 · 7 comments
Assignees

Comments

@JamesBonddu
Copy link

JamesBonddu commented Oct 27, 2024

What happened:
deploy karmada in kind

https://karmada.io/zh/docs/installation/#%E5%9C%A8-kind-%E9%9B%86%E7%BE%A4%E4%B8%AD%E5%AE%89%E8%A3%85-karmada

kubectl apply -k artifacts/overlays/nodeport-mode

Events:
  Type     Reason     Age                 From               Message
  ----     ------     ----                ----               -------
  Normal   Scheduled  105s                default-scheduler  Successfully assigned karmada-system/karmada-dashboard-api-864f449d8c-8ggkr to host-control-plane
  Normal   Pulling    105s                kubelet            Pulling image "karmada/karmada-dashboard-api:main"
  Normal   Pulled     92s                 kubelet            Successfully pulled image "karmada/karmada-dashboard-api:main" in 6.745s (12.724s including waiting). Image size: 36592844 bytes.
  Normal   Created    49s (x4 over 92s)   kubelet            Created container karmada-dashboard-api
  Normal   Pulled     49s (x3 over 91s)   kubelet            Container image "karmada/karmada-dashboard-api:main" already present on machine
  Normal   Started    48s (x4 over 92s)   kubelet            Started container karmada-dashboard-api
  Warning  Unhealthy  48s (x2 over 92s)   kubelet            Readiness probe failed: Get "http://10.176.0.13:8000/readyz": dial tcp 10.176.0.13:8000: connect: connection refused
  Warning  BackOff    21s (x10 over 90s)  kubelet            Back-off restarting failed container karmada-dashboard-api in pod karmada-dashboard-api-864f449d8c-8ggkr_karmada-system(3c11aba7-2d74-43ca-9088-1af2b98192eb)



root@karmada-host-control-plane:/# kubectl get pods -n karmada-system
NAME                                           READY   STATUS             RESTARTS       AGE
etcd-0                                         1/1     Running            0              29m
karmada-aggregated-apiserver-d6cbbb985-x4dbc   1/1     Running            0              28m
karmada-apiserver-ff6bdc958-fffl5              1/1     Running            0              29m
karmada-controller-manager-969d95b9b-p44bh     1/1     Running            0              28m
karmada-dashboard-api-5c965cc864-n2rbp         0/1     CrashLoopBackOff   7 (111s ago)   12m
karmada-dashboard-web-5cff8cbcbc-b2kbs         1/1     Running            0              23m
karmada-scheduler-59b7c9998-96sl6              1/1     Running            0              28m
karmada-webhook-58d45f45fc-5h47g               1/1     Running            0              28m
kube-controller-manager-6b49c4d6b9-cmcck       1/1     Running            0              28m
root@karmada-host-control-plane:/# kubectl logs karmada-dashboard-api-5c965cc864-n2rbp -n karmada-system
I1027 09:58:49.252435       1 api.go:77] "Starting Karmada Dashboard API" version="0.0.0-dev"
I1027 09:58:49.252529       1 init.go:71] "Using kubeconfig" kubeconfig="/etc/kubeconfig"
I1027 09:58:49.253442       1 client.go:25] Use context karmada-apiserver
E1027 09:58:49.253545       1 init.go:177] Could not init client config: invalid configuration: [context was not found for specified context: karmada-apiserver, cluster has no server defined]

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# uname -a
Linux iZj6c90gahowqyaz95yncqZ 5.10.0-32-amd64 #1 SMP Debian 5.10.223-1 (2024-08-10) x86_64 GNU/Linux
root@iZj6c90gahowqyaz95yncqZ:
/dashboard# docker --version
Docker version 20.10.24, build 297e128

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:
@JamesBonddu JamesBonddu added the kind/bug Categorizes issue or PR as related to a bug. label Oct 27, 2024
@RainbowMango
Copy link
Member

cc @warjiang

@warjiang
Copy link
Contributor

/assign

@warjiang
Copy link
Contributor

@JamesBonddu can you provide more detail about your kubernetes cluster and karmada cluster info?
it lacks of context of karmada-apiserver, you can execute kubectl config get-contexts and paste the output here

@JamesBonddu
Copy link
Author

JamesBonddu commented Oct 28, 2024

sorry i lost the config, i deployed in this note, but got dashboard login bug

https://merciful-moat-5ab.notion.site/kubekey-install-k8s-12d70fad774b8028a247c6953b24beae?pvs=4

i subbmited this issue

#144

@RainbowMango
Copy link
Member

OK. let's continue the discussion on #144.
/close

@karmada-bot
Copy link
Collaborator

@RainbowMango: Closing this issue.

In response to this:

OK. let's continue the discussion on #144.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@RainbowMango
Copy link
Member

/remove-kind bug

@karmada-bot karmada-bot removed the kind/bug Categorizes issue or PR as related to a bug. label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants