Describe the bug
A clear and concise description of what the bug is.
Whether I change the accessKey and secretKey from values.yaml or set them with existingSecret the pod will CrashLoop. The custom values even show correctly in helm get notes minio. Everything starts up fine when leaving accessKey and secretKey defaults.
pod logs show:
ERROR Unable to initialize server switching into safe-mode: Unable to initialize config system: Invalid credentials
Version of Helm and Kubernetes:
Helm 3.0.2 / K3S v1.16.3-k3s.2
Which chart:
stable/minio 5.0.1
since i was reusing the same PV, i was unaware that there was a hidden dir ".minio.sys" which contained encrypted configs that was created from the original accesskey and secretkey. I deleted .minio.sys/ and everything was fine.
Most helpful comment
since i was reusing the same PV, i was unaware that there was a hidden dir ".minio.sys" which contained encrypted configs that was created from the original accesskey and secretkey. I deleted .minio.sys/ and everything was fine.