连接集群后agent pod无法启动

[root@k8s-master-01 t]# helm ls
NAME                                    REVISION        UPDATED                         STATUS          CHART                           NAMESPACE 
chartmuseum                             1               Wed Nov 14 17:31:48 2018        DEPLOYED        chartmuseum-1.6.1               c7n-system
chartmuseum-pvc                         1               Wed Nov 14 17:30:05 2018        DEPLOYED        persistentvolumeclaim-0.1.0     c7n-system
choerodon-cluster-agent-dhph-test-k8s   1               Tue Mar 26 11:33:41 2019        DEPLOYED        choerodon-cluster-agent-0.14.0  choerodon 
winning-flee                            1               Fri Oct 26 16:32:20 2018        FAILED          nfs-provisioner-0.1.0           default   
[root@k8s-master-01]# kubectl logs -f choerodon-cluster-agent-dhph-test-k8s-5f76d6bd9f-h92c7 -n choerodon                                                                                       I0326 13:43:44.174281       7 agent.go:123] KubeClient init success.
I0326 13:43:44.174323       7 agent.go:125] Starting connect to tiller...
I0326 13:43:44.174565       7 agent.go:127] Tiller connect success
I0326 13:43:44.174571       7 agent.go:287] check k8s role binding...
E0326 13:43:44.182844       7 agent.go:290] check role binding failed pods is forbidden: User "system:serviceaccount:choerodon:choerodon-cluster-agent-dhph-test-k8s" cannot list pods at the cluster scope

你好,请提供安装agent时的helm命令及k8s版本相关信息,谢谢

您好,我们已经解决了该问题是由于RBAC需要创建choerodon相关权限。