kubesphere部署minio的机器挂掉后minio不会其他机器部署

johnhuster · 2022年3月23日

创建部署问题时，请参考下面模板，你提供的信息越多，越容易及时获得解答。如果未按模板创建问题，管理员有权关闭问题。
确保帖子格式清晰易读，用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题，不能指望别人花上半个小时给你解答。

操作系统信息
例如：ubuntu20.04

Kubernetes版本信息
将 kubectl version 命令执行结果贴在下方

Client Version: version.Info{Major:“1”, Minor:“20”, GitVersion:“v1.20.4”, GitCommit:“e87da0bd6e03ec3fea7933c4b5263d151aafd07c”, GitTreeState:“clean”, BuildDate:“2021-02-18T16:12:00Z”, GoVersion:“go1.15.8”, Compiler:“gc”, Platform:“linux/amd64”}

Server Version: version.Info{Major:“1”, Minor:“20”, GitVersion:“v1.20.4”, GitCommit:“e87da0bd6e03ec3fea7933c4b5263d151aafd07c”, GitTreeState:“clean”, BuildDate:“2021-02-18T16:03:00Z”, GoVersion:“go1.15.8”, Compiler:“gc”, Platform:“linux/amd64”}

容器运行时
将 docker version / crictl version / nerdctl version 结果贴在下方

Client:

Version: 20.10.7

API version: 1.41

Go version: go1.13.8

Git commit: 20.10.7-0ubuntu5~20.04.2

Built: Mon Nov 1 00:34:17 2021

OS/Arch: linux/amd64

Context: default

Experimental: true

Server:

Engine:

Version: 20.10.7

API version: 1.41 (minimum version 1.12)

Go version: go1.13.8

Git commit: 20.10.7-0ubuntu5~20.04.2

Built: Fri Oct 22 00:45:53 2021

OS/Arch: linux/amd64

Experimental: false

containerd:

Version: 1.5.5-0ubuntu3~20.04.2

GitCommit:

runc:

Version: 1.0.0~rc95-0ubuntu1~20.04.2

GitCommit:

docker-init:

Version: 0.19.0

GitCommit:

KubeSphere版本信息
例如：v3.1.,kk安装，minio pod日志如下：

kubectl describe po minio-f69748945-xf77c -n kubesphere-system

Name: minio-f69748945-xf77c

Namespace: kubesphere-system

Priority: 0

Node: <none>

Labels: app=minio

            pod-template-hash=f69748945

            release=ks-minio

Annotations: checksum/config: 4232ca8fd88fabeeb80679894e8d3f826a8b4280548882d0873609368b80bb35

            checksum/secrets: f9625c177e0e74a3b9997c3c65189ebffcfbde7aaa910de0ba38b48b032c1a96

Status: Pending

IP:

IPs: <none>

Controlled By: ReplicaSet/minio-f69748945

Containers:

minio:

Image:      minio/minio:RELEASE.2019-08-07T01-59-21Z

Port:       9000/TCP

Host Port:  0/TCP

Command:

  /bin/sh

  -ce

  /usr/bin/docker-entrypoint.sh minio -C /root/.minio/ server /data

Requests:

  cpu:      250m

  memory:   256Mi

Liveness:   http-get http://:service/minio/health/live delay=5s timeout=1s period=30s #success=1 #failure=3

Readiness:  http-get http://:service/minio/health/ready delay=5s timeout=1s period=15s #success=1 #failure=3

Environment:

  MINIO_ACCESS_KEY:  <set to the key 'accesskey' in secret 'minio'>  Optional: false

  MINIO_SECRET_KEY:  <set to the key 'secretkey' in secret 'minio'>  Optional: false

  MINIO_BROWSER:     on

Mounts:

  /data from export (rw)

  /root/.minio/ from minio-config-dir (rw)

  /var/run/secrets/kubernetes.io/serviceaccount from ks-minio-token-4kfc6 (ro)

Conditions:

Type Status

PodScheduled False

Volumes:

export:

Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)

ClaimName:  minio

ReadOnly:   false

minio-user:

Type:        Secret (a volume populated by a Secret)

SecretName:  minio

Optional:    false

minio-config-dir:

Type:       EmptyDir (a temporary directory that shares a pod's lifetime)

Medium:     

SizeLimit:  <unset>

ks-minio-token-4kfc6:

Type:        Secret (a volume populated by a Secret)

SecretName:  ks-minio-token-4kfc6

Optional:    false

QoS Class: Burstable

Node-Selectors: <none>

Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s

             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s

Events:

Type Reason Age From Message

Warning FailedScheduling 4h14m default-scheduler 0/4 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn’t tolerate, 1 node(s) were unschedulable, 2 node(s) had volume node affinity conflict.