kuboard启动报错解决

问题场景：

k8s单机集群在从1.23升级至1.24之后，发现kuboard出现报错无法登录。

---

问题描述

报错信息如下：
[root@node1 k8s]# kubectl -n kuboard logs -f kuboard-v3-84f9bf8bfc-c97bx
KUBOARD_ENDPOINT http://192.168.1.202:30080
eyJhbGciOiJSUzI1NiIsImtpZCI6Ik5MVE5pa1RYYW9mN0JyY1RPS1piTTlheEtGNHh2SVVhcVlid09tM0NWdTQifQ.eyJhdWQiOlsiaHR0cHM6Ly9rdWJlcm5ldGVzLmRlZmF1bHQuc3ZjLmNsdXN0ZXIubG9jYWwiXSwiZXhwIjoxNzQwNzAwMDU1LCJpYXQiOjE3MDkxNjQwNTUsImlzcyI6Imh0dHBzOi8va3ViZXJuZXRlcy5kZWZhdWx0LnN2Yy5jbHVzdGVyLmxvY2FsIiwia3ViZXJuZXRlcy5pbyI6eyJuYW1lc3BhY2UiOiJrdWJvYXJkIiwicG9kIjp7Im5hbWUiOiJrdWJvYXJkLXYzLTg0ZjliZjhiZmMtYzk3YngiLCJ1aWQiOiI0NTZmNjNlMC1kN2FiLTQ3NGYtOTEwMC01NTc4MGRlNWQ0OGYifSwic2VydmljZWFjY291bnQiOnsibmFtZSI6Imt1Ym9hcmQtYm9vc3RyYXAiLCJ1aWQiOiI2ZDRiMTc5MS1hNjU4LTQ4MmUtYTg1ZS0xNWM1NDlkODlhNTkifSwid2FybmFmdGVyIjoxNzA5MTY3NjYyfSwibmJmIjoxNzA5MTY0MDU1LCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6a3Vib2FyZDprdWJvYXJkLWJvb3N0cmFwIn0.spoZMDeSV86S9S8jpbn9PKoVtfBClr_nSOiKjlgGLQf7bkKvVSj5Hgo_lTyMFUzk-S8IrgHMW6-K0EBF51N6CdubuHGa8222-VWqbMW_TEUNHp4S4UDiY3h2Z8U4en2-DiWomIowgJ8CkvYTI3NTaDMgooKHPJxmG3YrhBzzF9xrJA13dCWm-IlNq4vFNW_ib_qOqESMDAL6HUg1kA4zcd8M0IXz8beM_zDkbO0oHgIcwqVka1Cof6wPVkQgbfSxZQV3puPitiH1BRoQc8dbs8rIzzyEAovEPuiRr1ylslUr-hUvi_P8if3kPaRrqqxeUdA-u3042igkSMmaTkaoQQ
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 113 100 113 0 0 7533 0 --:–:-- --:–:-- --:–:-- 7533
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 113 100 113 0 0 10272 0 --:–:-- --:–:-- --:–:-- 10272
[{
“kind”: “NodeList”,
“apiVersion”: “v1”,
“metadata”: {
“resourceVersion”: “78659”
},
“items”: []
},{
“kind”: “NodeList”,
“apiVersion”: “v1”,
“metadata”: {
“resourceVersion”: “78659”
},
“items”: []
}]

start kuboard-agent-server
当前 Kuboard 在 K8S 中运行，etcd 独立部署
认证模块：使用本地用户库
启动 kuboard-sso
设置日志级别为 info
time=“2024-02-28T23:47:51Z” level=info msg=“config using log level: info”
time=“2024-02-28T23:47:51Z” level=info msg=“config issuer: http://192.168.1.202:30080/sso”
time=“2024-02-28T23:47:51Z” level=info msg=“config storage: etcd”
time=“2024-02-28T23:47:51Z” level=info msg=“config static client: KuboardApp”
time=“2024-02-28T23:47:51Z” level=info msg=“config connector: default”
time=“2024-02-28T23:47:51Z” level=info msg=“config skipping approval screen”
time=“2024-02-28T23:47:51Z” level=info msg=“config signing keys expire after: 6h0m0s”
time=“2024-02-28T23:47:51Z” level=info msg=“config id tokens valid for: 168h0m0s”
time=“2024-02-28T23:47:51Z” level=info msg=“config device requests valid for: 5m0s”
设置日志级别为 info
[LOG] 2024/02/29 - 07:47:54.193 | /initializekuboard.InitializeEtcd 39 | info | 初始化 ./init-etcd-scripts/audit-policy-once.yaml
{“level”:“warn”,“ts”:“2024-02-29T07:47:56.173+0800”,“caller”:“clientv3/retry_interceptor.go:61”,“msg”:“retrying of unary invoker failed”,“target”:“endpoint://client-55914f2a-7937-4583-acd1-d53227cbeb1c/”,“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

---

解决方案：

参考url:https://github.com/eip-work/kuboard-press/issues/449