eip-work / kuboard-press

Kuboard 是基于 Kubernetes 的微服务管理界面。同时提供 Kubernetes 免费中文教程,入门教程,最新版本的 Kubernetes v1.23.4 安装手册,(k8s install) 在线答疑,持续更新。
https://kuboard.cn/
21.78k stars 1.49k forks source link

kuboard-v3确定支持kubernetes-1.26.0 #405

Open YueChuang opened 1 year ago

YueChuang commented 1 year ago

我在本机启动了k8s单节点集群,版本是1.26.0,然后我按照kuboard官方的方式运行kuboard,但是一直不能运行成功,当我执行了官方的安装命令后,我发现在我的集群内创建了一个kuboard的命名空间,然后在空间内运行了两个pod,一个名叫kuboard-etcd,另一个叫kuboard-v3,而这个kuboard-v3显示的状态是running,但是一直在报错。 报错信息如下: start kuboard-agent-server 当前 Kuboard 在 K8S 中运行,etcd 独立部署 启动内置的 QuestDB


/ \ _ | || | ) | | | | | | |/ \/ | | | | | \ | || | || | /_ \ || || | |) | __\_,|_||/__|/|/ www.questdb.io

/questdb/bin/questdb.sh: line 66: ps: command not found JAVA: /questdb/bin/java QuestDB server 6.0.4 Copyright (C) 2014-2023, all rights reserved.

认证模块:使用本地用户库 启动 kuboard-sso 设置日志级别为 info time="2023-04-26T02:13:15Z" level=info msg="config using log level: info" time="2023-04-26T02:13:15Z" level=info msg="config issuer: http://10.32.254.126:30080/sso" time="2023-04-26T02:13:15Z" level=info msg="config storage: etcd" time="2023-04-26T02:13:15Z" level=info msg="config static client: KuboardApp" time="2023-04-26T02:13:15Z" level=info msg="config connector: default" time="2023-04-26T02:13:15Z" level=info msg="config skipping approval screen" time="2023-04-26T02:13:15Z" level=info msg="config signing keys expire after: 6h0m0s" time="2023-04-26T02:13:15Z" level=info msg="config id tokens valid for: 168h0m0s" time="2023-04-26T02:13:15Z" level=info msg="config device requests valid for: 5m0s" 设置日志级别为 info [LOG] 2023/04/26 - 10:13:18.387 | /common/etcd.client_config 24 | info | KUBOARD_ETCD_ENDPOINTS=[] [LOG] 2023/04/26 - 10:13:18.387 | /common/etcd.client_config 52 | info | {[] 0s 1s 0s 0s 0 0 false [] false} [LOG] 2023/04/26 - 10:13:18.389 | /initializekuboard.InitializeEtcd 39 | info | 初始化 ./init-etcd-scripts/audit-policy-once.yaml {"level":"warn","ts":"2023-04-26T10:13:20.217+0800","caller":"clientv3/retry_interceptor.go:61","msg":"retrying of unary invoker failed","target":"endpoint://client-5d9037cd-0b18-49d8-ac4f-5f9bcbc3822c/","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: Error while dialing dial tcp: missing address\""} failed to initialize server: server: failed to list connector objects from storage: context deadline exceeded

请问这个这么解决?