I have been trying to do a helm upgrade of airbyte from v0.39.1-alpha to v0.39.34-alpha via fluxcd and getting helm upgrade failed messages, apparently from the minio subchart secrets template. Apparently it can't locate the root-password from an existing secret?? Airbyte seems to have jumped from version 7.3.2 of bitnami minio subchart (which is no longer available??) to version 11.6.2 so it's possible a lot has changed in minio. Should I manually delete the airbyte-minio secret and try the upgrade again? Should I set `minio.auth.rootUser`/`rootPassword` to the same defaults as Airbyte (`minio`/`minio123`)? Do I have to manually delete the minio pods?

Im facing same problem when trying to deploy using Helm chart. Otherwise, when I deploy using Kustomize it works.

FYI - my solution was primarily to create a new kube secret for minio's root-user & root-password and set

minio.auth.existingSecret

in the airbyte values (i used the

minio

&

minio123

values).

apiVersion: v1
kind: Secret
type: Opaque
metadata:
  name: airbyte-minio-root
  namespace: airbyte
data:
  root-user: bWluaW8=
  root-password: bWluaW8xMjM=

I also deleted the old minio PVC+PV, but I'm not sure if that's really required. I did have some hiccups, which I didn't document, but I recall them as simple things. Everything still works, this is just a documentation issue I think (although, in my opinion, the old minio access management in the airbyte chart needs to be dropped too)