kubesphere-system如何手动添加minio

clf

创建部署问题时，请参考下面模板：
在最小安装kubesphere之后，想安装应用商店。
发现kubesphere-system少了一个pod/minio，现在想手动添加这个pod，请问哪里可以找到这个配置文件呢？

十分感谢！

yuswift

kubectl get cc ks-installer -n kubesphere-system -o yaml 看看一般是会自动被创建的

clf

yuswift 你好下面是我的输出信息
apiVersion: installer.kubesphere.io/v1alpha1
kind: ClusterConfiguration
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{“apiVersion”:“installer.kubesphere.io/v1alpha1”,“kind”:“ClusterConfiguration”,“metadata”:{“annotations”:{},“labels”:{“version”:“v3.0.0”},“name”:“ks-installer”,“namespace”:“kubesphere-system”},“spec”:{“alerting”:{“enabled”:false},“auditing”:{“enabled”:false},“authentication”:{“jwtSecret”:""},“common”:{“es”:{“elasticsearchDataVolumeSize”:“20Gi”,“elasticsearchMasterVolumeSize”:“4Gi”,“elkPrefix”:“logstash”,“logMaxAge”:7},“etcdVolumeSize”:“20Gi”,“minioVolumeSize”:“20Gi”,“mysqlVolumeSize”:“20Gi”,“openldapVolumeSize”:“2Gi”,“redisVolumSize”:“2Gi”},“console”:{“enableMultiLogin”:true,“port”:19123},“devops”:{“enabled”:false,“jenkinsJavaOpts_MaxRAM”:“2g”,“jenkinsJavaOpts_Xms”:“512m”,“jenkinsJavaOpts_Xmx”:“512m”,“jenkinsMemoryLim”:“2Gi”,“jenkinsMemoryReq”:“1500Mi”,“jenkinsVolumeSize”:“8Gi”},“etcd”:{“endpointIps”:“localhost”,“monitoring”:false,“port”:2379,“tlsEnable”:true},“events”:{“enabled”:false,“ruler”:{“enabled”:true,“replicas”:2}},“logging”:{“enabled”:false,“logsidecarReplicas”:2},“metrics_server”:{“enabled”:false},“monitoring”:{“prometheusMemoryRequest”:“400Mi”,“prometheusVolumeSize”:“20Gi”},“multicluster”:{“clusterRole”:“none”},“networkpolicy”:{“enabled”:false},“notification”:{“enabled”:false},“openpitrix”:{“enabled”:true},“persistence”:{“storageClass”:“local-volume”},“servicemesh”:{“enabled”:false}}}
creationTimestamp: “2021-01-25T06:28:39Z”
generation: 46
labels:
version: v3.0.0
name: ks-installer
namespace: kubesphere-system
resourceVersion: “112700624”
selfLink: /apis/installer.kubesphere.io/v1alpha1/namespaces/kubesphere-system/clusterconfigurations/ks-installer
uid: 39913582-943a-4ddc-9bd6-7971427595ba
spec:
alerting:
enabled: false
auditing:
enabled: false
authentication:
jwtSecret: ""
common:
es:
elasticsearchDataVolumeSize: 20Gi
elasticsearchMasterVolumeSize: 4Gi
elkPrefix: logstash
logMaxAge: 7
etcdVolumeSize: 20Gi
minioVolumeSize: 20Gi
mysqlVolumeSize: 20Gi
openldapVolumeSize: 2Gi
redisVolumSize: 2Gi
console:
enableMultiLogin: true
port: 19123
devops:
enabled: false
jenkinsJavaOpts_MaxRAM: 2g
jenkinsJavaOpts_Xms: 512m
jenkinsJavaOpts_Xmx: 512m
jenkinsMemoryLim: 2Gi
jenkinsMemoryReq: 1500Mi
jenkinsVolumeSize: 8Gi
etcd:
endpointIps: localhost
monitoring: false
port: 2379
tlsEnable: true
events:
enabled: false
ruler:
enabled: true
replicas: 2
logging:
enabled: false
logsidecarReplicas: 2
metrics_server:
enabled: false
monitoring:
prometheusMemoryRequest: 400Mi
prometheusVolumeSize: 20Gi
multicluster:
clusterRole: none
networkpolicy:
enabled: false
notification:
enabled: false
openpitrix:
enabled: true
persistence:
storageClass: local-volume
servicemesh:
enabled: false
status:
clusterId: 2928f706-5fa0-11eb-af34-02420a056003
core:
enabledTime: 2021-01-26T14:30:05CST
status: enabled
minio:
enabledTime: 2021-01-26T14:33:03CST
status: enabled
monitoring:
enabledTime: 2021-01-26T14:31:12CST
status: enabled
mysql:
enabledTime: 2021-01-26T14:33:05CST
status: enabled
openldap:
enabledTime: 2021-01-26T14:29:32CST
status: enabled
openpitrix:
enabledTime: 2021-01-26T14:33:35CST
status: enabled
redis:
enabledTime: 2021-01-26T14:29:26CST
status: enabled

clf

yuswift 有点特别的是，我的sc是基于local的就是说我要手动创建pv/pvc的。有可能因为这个导致我minio一直被跳过了所以我想手动添加这个pod!

yuswift

但是你这里显示的minio已经被enable了这是我的minio yaml 你可以参考一下
apiVersion: apps/v1 kind: Deployment metadata: annotations: deployment.kubernetes.io/revision: "1" meta.helm.sh/release-name: ks-minio meta.helm.sh/release-namespace: kubesphere-system creationTimestamp: "2020-10-22T16:16:44Z" generation: 1 labels: app: minio app.kubernetes.io/managed-by: Helm chart: minio-2.5.16 heritage: Helm release: ks-minio name: minio namespace: kubesphere-system resourceVersion: "1392328" selfLink: /apis/apps/v1/namespaces/kubesphere-system/deployments/minio uid: 077f29b3-5b95-45f8-8e36-121ced5bc567 spec: progressDeadlineSeconds: 600 replicas: 1 revisionHistoryLimit: 10 selector: matchLabels: app: minio release: ks-minio strategy: rollingUpdate: maxSurge: 100% maxUnavailable: 0 type: RollingUpdate template: metadata: annotations: checksum/config: c6cc7f4b40064dffd59b339e133fa4819f787573ee18e1d001435aa4daff8ba2 checksum/secrets: f9625c177e0e74a3b9997c3c65189ebffcfbde7aaa910de0ba38b48b032c1a96 creationTimestamp: null labels: app: minio release: ks-minio name: minio spec: containers: - command: - /bin/sh - -ce - /usr/bin/docker-entrypoint.sh minio -C /root/.minio/ server /data env: - name: MINIO_ACCESS_KEY valueFrom: secretKeyRef: key: accesskey name: minio - name: MINIO_SECRET_KEY valueFrom: secretKeyRef: key: secretkey name: minio - name: MINIO_BROWSER value: "on" image: minio/minio:RELEASE.2019-08-07T01-59-21Z imagePullPolicy: IfNotPresent livenessProbe: failureThreshold: 3 httpGet: path: /minio/health/live port: service scheme: HTTP initialDelaySeconds: 5 periodSeconds: 30 successThreshold: 1 timeoutSeconds: 1 name: minio ports: - containerPort: 9000 name: service protocol: TCP readinessProbe: failureThreshold: 3 httpGet: path: /minio/health/ready port: service scheme: HTTP initialDelaySeconds: 5 periodSeconds: 15 successThreshold: 1 timeoutSeconds: 1 resources: requests: cpu: 250m memory: 256Mi terminationMessagePath: /dev/termination-log terminationMessagePolicy: File volumeMounts: - mountPath: /data name: export - mountPath: /root/.minio/ name: minio-config-dir dnsPolicy: ClusterFirst restartPolicy: Always schedulerName: default-scheduler securityContext: {} serviceAccount: ks-minio serviceAccountName: ks-minio terminationGracePeriodSeconds: 30 volumes: - name: export persistentVolumeClaim: claimName: minio - name: minio-user secret: defaultMode: 420 secretName: minio - emptyDir: {} name: minio-config-dir

clf

yuswift 你好感谢你帮助但是我决定这个集群重新安装一次试试。现在有另外的集群也是卡在安装minio这一步
报错信息如下：

按下面提示的步骤，我发现步骤3 4 都没有相应的日志。。。

clf

Feynman yuswift 我重新安装的集群的时候，很多时候他会自动帮我跳过某些组件（比如跳过minio、跳过openldap）有没有可能是我卸载不干净？HELM的版本过低？我的helm的版本是v2.12.3。

Feynman

clf k8s 集群的默认的存储有问题，得有一个可以动态创建挂盘的 default sc 才行。localpv 应该不支持这个特性

clf

Feynman 的 default sc 才行。loca

Feynman 是的 localpv不支持动态制卷会有很多麻烦您有什么推荐的吗比如ceph还是什么业界更为流行的分布式存储解决方案呢？

Feynman

clf 简单易用易部署的可以用 NFS、openebs、longhorn 都可以在开发测试环境，生产环境的存储建议有存储运维人员来维护或用商业存储

clf

Feynman 还有请问一下，重启kubesphere集群的正确姿势是什么？是直接运行官方给的kubesphere-delete.sh脚本然后重新安装吗？

Feynman

clf 那个脚本是卸载不是重启。为啥还在安装 2.1.1 呢？ 3.0.0 是最新的版本

clf

Feynman 我安装的是v3.0.0版本。是helm版本太低了吗？总会出现卸载不干净，重新安装跳过某些组件，具体表现为pod没有起来，而kubectl get cc ks-installer -n kubesphere-system -o yaml又显示在运行

clf

Feynman 比如现在

缺少了openldap。但是执行kubectl get cc ks-installer -n kubesphere-system -o yaml

clf

组件残缺原因可能有以下几个：

helm版本过低导致卸载可能不太干净，将2.X版本升级到3.X
sc为local没有动态制卷的能力，引入longhorn插件。