当前位置：首页 > news >正文

k8s下部署kuboard

news 2026/3/27 0:53:59

环境：

OS:Centos 7

1.下载yaml文件
[root@master kuboard]# cd /root/my_yaml/kuboard
[root@master kuboard]# wget https://addons.kuboard.cn/kuboard/kuboard-v3-swr.yaml

2.部署
[root@master kuboard]# cd /root/my_yaml/kuboard
[root@master kuboard]# kubectl apply -f kuboard-v3-swr.yaml

3.查看启动情况

[root@master kuboard]# kubectl get pods -n kuboard
NAME                          READY   STATUS    RESTARTS      AGE
kuboard-etcd-6vmkm            1/1     Running   0             8m46s
kuboard-v3-7979bc788f-r2zgb   0/1     Running   5 (76s ago)   8m46s

4.查看报错信息
启动报错误:
[root@master kuboard]# kubectl logs kuboard-v3-7979bc788f-r2zgb -n kuboard

认证模块：使用本地用户库
启动 kuboard-sso
设置日志级别为 info
time="2025-09-29T06:36:11Z" level=info msg="config using log level: info"
time="2025-09-29T06:36:11Z" level=info msg="config issuer: http://192.168.1.105:30080/sso"
time="2025-09-29T06:36:11Z" level=info msg="config storage: etcd"
time="2025-09-29T06:36:11Z" level=info msg="config static client: KuboardApp"
time="2025-09-29T06:36:11Z" level=info msg="config connector: default"
time="2025-09-29T06:36:11Z" level=info msg="config skipping approval screen"
time="2025-09-29T06:36:11Z" level=info msg="config signing keys expire after: 6h0m0s"
time="2025-09-29T06:36:11Z" level=info msg="config id tokens valid for: 168h0m0s"
time="2025-09-29T06:36:11Z" level=info msg="config device requests valid for: 5m0s"
设置日志级别为 info
[LOG] 2025/09/29 - 14:36:14.063   | /common/etcd.client_config                                    24 |  info | KUBOARD_ETCD_ENDPOINTS=[]
[LOG] 2025/09/29 - 14:36:14.063   | /common/etcd.client_config                                    52 |  info | {[] 0s 1s 0s 0s 0 0 <nil>   false [] <nil> <nil> <nil> false}
[LOG] 2025/09/29 - 14:36:14.064   | /initializekuboard.InitializeEtcd                             39 |  info | 初始化 ./init-etcd-scripts/audit-policy-once.yaml
{"level":"warn","ts":"2025-09-29T14:36:16.003+0800","caller":"clientv3/retry_interceptor.go:61","msg":"retrying of unary invoker failed","target":"endpoint://client-34457e91-47b0-40ac-a3b9-09ad0f302188/","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

5.编辑配置文件
[root@master kuboard]# kubectl get cm -n kuboard
NAME DATA AGE
kube-root-ca.crt 1 5m18s
kuboard-v3-config 8 5m18s
[root@master ~]# kubectl edit cm kuboard-v3-config -n kuboard

搜索此配置项,将此配置项替换
替换前:
KUBOARD_SERVER_NODE_PORT: '30080'

替换后:(k8s节点的任意IP)
KUBOARD_ENDPOINT: 'http://192.168.1.105:30080'

6.删除之前的 pod 让它自己拉起来
[root@master kuboard]# kubectl delete pod kuboard-v3-7979bc788f-r2zgb -n kuboard
pod "kuboard-v3-7979bc788f-r2zgb" deleted

7.查看pod

[root@master kuboard]# kubectl get pods -n kuboard
NAME                          READY   STATUS    RESTARTS   AGE
kuboard-etcd-6vmkm            1/1     Running   0          40m
kuboard-v3-7979bc788f-hzd8j   1/1     Running   0          29m

详细信息

[root@master kuboard]# kubectl get pods -n kuboard -o wide
NAME                          READY   STATUS    RESTARTS   AGE   IP              NODE     NOMINATED NODE   READINESS GATES
kuboard-etcd-6vmkm            1/1     Running   0          41m   192.168.1.108   master   <none>           <none>
kuboard-v3-7979bc788f-hzd8j   1/1     Running   0          30m   10.244.104.7    node2    <none>           <none>