minio: expand decommission pools in argocd

expand the tenant (tenant.pools.size) in minio

1.install tenant from appofapps, pool name: pool-0

2.to expand tenant, add pool-1 into application yaml of tenant,check into git repo;

expand pools were OK. tenant: it worked.

3.If want to decommission pools, run the following commands.

#create and login a minio client pod in k8s

kubectl run minioclient -i -t --image=minio/mc --command -- /bin/sh -c 'echo hello;sleep 3600'

kubectl exec -i -t -n default minioclient -c minioclient -- sh

Note that the following commands need to be run in the pod of k8s.

#minio config

mc alias set dev4 http://minio.tenant.svc.cluster.local:80 minio minio123 --api s3v4

  1. #check the pools status

mc admin decommission status dev4

#decommission pool (it will automatically migrate data.)

mc admin decommission start dev4 http://myminio-pool-1-{0...3}.myminio-hl.tenant.svc.cluster.local/export{0...3}/data

  1. delete pool-1 in tenant application yaml, check into git repo;

tenant: it worked. ( pool-0 )

复制代码
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: tenant
  namespace: argocd
  finalizers:
  - resources-finalizer.argocd.argoproj.io
spec:
  project: default
  source:
    repoURL: 'https://operator.min.io/'
    targetRevision: 5.0.6
    helm:
      parameters:
        - name: 'tenant.pools[0].storageClassName'
          value: cinder
        - name: 'tenant.pools[0].name'
          value: 'pool-0'
        - name: 'tenant.pools[0].servers'
          value: '4'
        - name: 'tenant.pools[0].size'
          value: 4Gi
        - name: 'tenant.pools[0].volumesPerServer'
          value: '4'
#       - name: 'tenant.pools[1].storageClassName'
#         value: cinder
#       - name: 'tenant.pools[1].name'
#         value: 'pool-1'
#       - name: 'tenant.pools[1].servers'
#         value: '4'
#       - name: 'tenant.pools[1].size'
#         value: 6Gi
#       - name: 'tenant.pools[1].volumesPerServer'
#         value: '4'
        - name: tenant.certificate.requestAutoCert
          value: 'false'
        - name: 'tenant.buckets[0].name'
          value: 'artifacts'
        - name: 'tenant.buckets[1].name'
          value: 'test'
    chart: tenant
  destination:
    server: 'https://kubernetes.default.svc'
    namespace: tenant
  syncPolicy:
    automated: {}
    syncOptions:
      - CreateNamespace=true
相关推荐
b***74888 天前
2025年前端开发新方向预测
剪枝·activemq·argocd
研究司马懿21 天前
【ETCD】ETCD——confd配置管理
数据库·golang·自动化·运维开发·etcd·argocd·gitops
研究司马懿23 天前
【ETCD】ETCD单节点二进制部署(TLS)
数据库·chrome·云原生·运维开发·etcd·argocd·gitops
老年DBA1 个月前
Kubernetes 上的 GitLab + ArgoCD 实践(三):使用 ArgoCD 打通 CD 流程
kubernetes·gitlab·argocd
老年DBA1 个月前
Kubernetes 上的 GitLab + ArgoCD 实践(二):使用自建 GitLab Runner 完善 CI 流程
kubernetes·gitlab·argocd
研究司马懿1 个月前
【GitOps】Argo CD app of apps
大数据·开发语言·elasticsearch·搜索引擎·云原生·argocd·gitops
虫师c2 个月前
GitOps实战:ArgoCD+Tekton打造云原生CI/CD流水线
git·ci/cd·云原生·kubernetes·argocd·tekton
hello_2502 个月前
GitOps:一种实现云原生的持续交付模型
架构·argocd
谭咏麟4 个月前
Argo CD持续交付工具部署
kubernetes·argocd·cicd
hwj运维之路5 个月前
GitOps实践指南:GitLab CI/CD + ArgoCD 实现 Kubernetes 自动化部署
ci/cd·gitlab·argocd