创建部署问题时,请参考下面模板,你提供的信息越多,越容易及时获得解答。如果未按模板创建问题,管理员有权关闭问题。
确保帖子格式清晰易读,用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题,不能指望别人花上半个小时给你解答。
操作系统信息
物理机,Ubuntu22.04,8C/16G
Kubernetes版本信息
将 kubectl version 命令执行结果贴在下方
root@master1:/opt/kubesphere/v4.2.0# kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.10", GitCommit:"7e54d50d3012cf3389e43b096ba35300f36e0817", GitTreeState:"clean", BuildDate:"2022-08-17T18:32:54Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.10", GitCommit:"7e54d50d3012cf3389e43b096ba35300f36e0817", GitTreeState:"clean", BuildDate:"2022-08-17T18:26:59Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"}
容器运行时
将 docker version / crictl version / nerdctl version 结果贴在下方
root@master1:/opt/kubesphere/v4.2.0# docker version
Client:
 Version:           24.0.9
 API version:       1.43
 Go version:        go1.20.13
 Git commit:        2936816
 Built:             Thu Feb  1 00:47:46 2024
 OS/Arch:           linux/amd64
 Context:           default
Server: Docker Engine - Community
 Engine:
  Version:          24.0.9
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.13
  Git commit:       fca702d
  Built:            Thu Feb  1 00:49:16 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.13
  GitCommit:        7c3aca7a610df76212171d200ca3811ff6096eb8
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
KubeSphere版本信息
v4.2.0。 在线安装。 使用kk安装。
问题是什么
报错日志是什么,最好有截图。
镜像拉取问题。老问题了,阿里云的容器镜像仓库会在拉取镜像达到一定频率次数时,直接限流,导致pod无法正常运行。
Events:
  Type     Reason   Age                    From     Message
  ----     ------   ----                   ----     -------
  Normal   BackOff  8m52s (x184 over 80m)  kubelet  Back-off pulling image "registry.cn-beijing.aliyuncs.com/kse/ks-console:v4.2.0-community"
  Warning  Failed   2m (x13 over 80m)      kubelet  Failed to pull image "registry.cn-beijing.aliyuncs.com/kse/ks-console:v4.2.0-community": rpc error: code = Unknown desc = context canceled
root@master1:/opt/kubesphere/v4.2.0# 
root@master1:/opt/kubesphere/v4.2.0# 
root@master1:/opt/kubesphere/v4.2.0# 
root@master1:/opt/kubesphere/v4.2.0# 
root@master1:/opt/kubesphere/v4.2.0# 
root@master1:/opt/kubesphere/v4.2.0# docker pull registry.cn-beijing.aliyuncs.com/kse/ks-console:v4.2.0-community
^C
root@master1:/opt/kubesphere/v4.2.0# kubectl get pod -A -o wide
NAMESPACE           NAME                                           READY   STATUS             RESTARTS   AGE     IP             NODE      NOMINATED NODE   READINESS GATES
kube-system         calico-kube-controllers-6f996c8485-hh5km       1/1     Running            0          92m     10.233.69.2    work1     <none>           <none>
kube-system         calico-node-dnrkn                              1/1     Running            0          92m     172.16.0.27    master3   <none>           <none>
kube-system         calico-node-f2msv                              1/1     Running            0          92m     172.16.0.25    master1   <none>           <none>
kube-system         calico-node-jddtm                              1/1     Running            0          92m     172.16.0.26    master2   <none>           <none>
kube-system         calico-node-wdnvm                              1/1     Running            0          92m     172.16.0.28    work1     <none>           <none>
kube-system         coredns-84f5b79b8b-4jnnj                       1/1     Running            0          92m     10.233.69.1    work1     <none>           <none>
kube-system         coredns-84f5b79b8b-8mc29                       1/1     Running            0          92m     10.233.69.4    work1     <none>           <none>
kube-system         kube-apiserver-master1                         1/1     Running            0          93m     172.16.0.25    master1   <none>           <none>
kube-system         kube-apiserver-master2                         1/1     Running            0          92m     172.16.0.26    master2   <none>           <none>
kube-system         kube-apiserver-master3                         1/1     Running            0          92m     172.16.0.27    master3   <none>           <none>
kube-system         kube-controller-manager-master1                1/1     Running            0          93m     172.16.0.25    master1   <none>           <none>
kube-system         kube-controller-manager-master2                1/1     Running            0          92m     172.16.0.26    master2   <none>           <none>
kube-system         kube-controller-manager-master3                1/1     Running            0          92m     172.16.0.27    master3   <none>           <none>
kube-system         kube-proxy-422cv                               1/1     Running            0          92m     172.16.0.25    master1   <none>           <none>
kube-system         kube-proxy-cq864                               1/1     Running            0          92m     172.16.0.27    master3   <none>           <none>
kube-system         kube-proxy-hcmnt                               1/1     Running            0          92m     172.16.0.28    work1     <none>           <none>
kube-system         kube-proxy-zq92j                               1/1     Running            0          92m     172.16.0.26    master2   <none>           <none>
kube-system         kube-scheduler-master1                         1/1     Running            0          93m     172.16.0.25    master1   <none>           <none>
kube-system         kube-scheduler-master2                         1/1     Running            0          92m     172.16.0.26    master2   <none>           <none>
kube-system         kube-scheduler-master3                         1/1     Running            0          92m     172.16.0.27    master3   <none>           <none>
kube-system         nodelocaldns-5r4ft                             1/1     Running            0          92m     172.16.0.25    master1   <none>           <none>
kube-system         nodelocaldns-bkj42                             1/1     Running            0          92m     172.16.0.27    master3   <none>           <none>
kube-system         nodelocaldns-c2j5n                             1/1     Running            0          92m     172.16.0.26    master2   <none>           <none>
kube-system         nodelocaldns-z5gt8                             1/1     Running            0          92m     172.16.0.28    work1     <none>           <none>
kube-system         openebs-localpv-provisioner-7bbcf865cd-wpgxg   1/1     Running            0          92m     10.233.69.0    work1     <none>           <none>
kubesphere-system   extensions-museum-554bfcccdd-9rrk8             1/1     Running            0          3m10s   10.233.69.13   work1     <none>           <none>
kubesphere-system   helm-install-ks-console-embed-wfxnv7-58c9n     0/1     Completed          0          84m     10.233.69.6    work1     <none>           <none>
kubesphere-system   ks-apiserver-5cd7fd44bb-wrxb5                  1/1     Running            0          6m57s   10.233.96.2    master3   <none>           <none>
kubesphere-system   ks-console-75785789dc-bw525                    0/1     ImagePullBackOff   0          5m9s    10.233.96.3    master3   <none>           <none>
kubesphere-system   ks-console-75b4db6cdf-hr9wx                    0/1     ImagePullBackOff   0          84m     10.233.97.2    master1   <none>           <none>
kubesphere-system   ks-console-embed-7455774f78-jzfs5              1/1     Running            0          80m     10.233.69.7    work1     <none>           <none>
kubesphere-system   ks-controller-manager-6fc8bbd47f-xdptb         1/1     Running            0          6m57s   10.233.97.3    master1   <none>           <none>
kubesphere-system   ks-posthog-6f5d89f985-p4kv6                    1/1     Running            0          86m     10.233.98.1    master2   <none>           <none>
root@master1:/opt/kubesphere/v4.2.0# 
临时解决方法
- 在其他机器下载容器镜像后放到所有节点。
- 希望容器镜像可以提供离线打包文件或者其他容器镜像仓库,阿里云的限制太影响部署。