创建部署问题时,请参考下面模板,你提供的信息越多,越容易及时获得解答。如果未按模板创建问题,管理员有权关闭问题。
确保帖子格式清晰易读,用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题,不能指望别人花上半个小时给你解答。
操作系统信息
rocky9
Kubernetes版本信息
v1.24.15
容器运行时
Version: 0.1.0
RuntimeName: containerd
RuntimeVersion: 1.6.21
RuntimeApiVersion: v1
KubeSphere版本信息
v3.4.0。 在线安装。在已有K8s上安装
问题是什么
ks-controller-manager状态CrashLoopBackOff,ks-controller-manager默认检测的calico-node命名空间是kube-system,而手动安装的calico默认命名空间是calico-system,如果设置ks-controller-manager检测calico-node的命名空间为calico-system?
ks-controller-manager日志:
W1211 13:18:26.851566 1 client_config.go:618] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
I1211 13:18:26.852267 1 server.go:197] setting up manager
I1211 13:18:26.871417 1 listener.go:44] “controller-runtime/metrics: Metrics server is starting to listen” addr=“:8080”
I1211 13:18:26.906037 1 reconciler.go:149] “controllers/Helm: Watching resource” group=“gateway.kubesphere.io” version=“v1alpha1” kind=“Nginx”
I1211 13:18:26.906052 1 helm_controller.go:76] configured watch gvk gateway.kubesphere.io/v1alpha1, Kind=Nginx chartPath /var/helm-charts/ingress-nginx maxConcurrentReconciles 8 reconcilePeriod 1m0s
I1211 13:18:26.906149 1 reconciler.go:149] “controllers/Helm: Watching resource” group=“gateway.kubesphere.io” version=“v1alpha1” kind=“Gateway”
I1211 13:18:26.906156 1 helm_controller.go:76] configured watch gvk gateway.kubesphere.io/v1alpha1, Kind=Gateway chartPath /var/helm-charts/gateway maxConcurrentReconciles 8 reconcilePeriod 1m0s
I1211 13:18:26.907012 1 loginrecord_controller.go:94] Setting up event handlers
I1211 13:18:26.907155 1 certificatesigningrequest_controller.go:93] Setting up event handlers
I1211 13:18:26.907495 1 clusterrolebinding_controller.go:98] Setting up event handlers
I1211 13:18:26.907621 1 globalrolebinding_controller.go:107] Setting up event handlers
I1211 13:18:26.907752 1 groupbinding_controller.go:95] Setting up event handlers
I1211 13:18:26.907874 1 group_controller.go:103] Setting up event handlers
W1211 13:18:26.908066 1 client_config.go:618] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
F1211 13:18:26.911579 1 provider.go:668] failed to get calico-node deployment in kube-system, err=daemonsets.apps “calico-node” not found