Self-Managed Instance of Gitlabs, New Values in Minio After Reconfiguring No Being Applied

Juan Perez 1 Reputation point

I need to reconfigure Minio after a standard Gitlab install via Helm Charts, would like to increase to 100GB from the 9GB installed, however any time I run the upgrade with the file change looks like successfully upgraded, but the changes have not been applied and Minio Browser still showing 9GB

email: ******************
install: true
gitlab-runner.runners.privileged: true
gitlab-runner.imagePullPolicy: IfNotPresent
edition: ce
domain: ******************
size: 100Gi
imagePullPolicy: IfNotPresent
imagePullPolicy: IfNotPresent

(looks like the indentation of my yaml file is gone!)

Then applied my changes

Found the problem when launching
kubectl get events -w -n gitlabs


Any ideas how to workaround or fix this issue?

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,557 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. SRIJIT-BOSE-MSFT 4,296 Reputation points Microsoft Employee

    @Juan Perez , Thank you for your question.

    If the Azure managed disk is already attached to a running VM, disk resize will fail.

    Before running kubectl edit pvc pvc-azuredisk operation, please make sure this PVC is not mounted by any pod (change the replica count to 0, this will terminate the pod and detach the disk, need wait a few minutes) otherwise there would be resize error. Now run kubectl edit pvc pvc-azuredisk to change azuredisk PVC size.

    Please refer to this GitHub PR for detailed instructions.


    Hope this helps.

    Please "Accept as Answer" if it helped, so that it can help others in the community looking for help on similar topics.

    0 comments No comments