Getting an error when upgrading airbyte on k8s from 0.40.2 to 0.40.14 in the

aibyte-chart-airbyte-worker

pod with the helm release:

Message: No bean of type [io.airbyte.config.persistence.split_secrets.SecretPersistence] exists for the given qualifier: @Named('secretPersistence'). Make sure the bean is not disabled by bean requirements (enable trace logging for 'io.micronaut.context.condition' to check) and if the bean is enabled then ensure the class is declared a bean and annotation processing is enabled (for Java and Kotlin the 'micronaut-inject-java' dependency should be configured as an annotation processor).

Seems the same problem as https://airbytehq.slack.com/archives/C021JANJ6TY/p1665149370573089 ? UPDATE: Due to @lucien his answer I know he was running 0.40.6 without problems. Upgrading from 0.40.2 to 0.40.6 succeeded. So this somewhat confirms this problem is introduced between 0.40.6 and 0.40.13. UPDATE2: Can it be something related to this commit in version 0.40.10? https://github.com/airbytehq/airbyte/commit/9abcbadd9316d3017a4573bc195f44e15b5a0dfb

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2777 to ensure timely resolution!

Hi! Thanks for the updates. Just to double check, were you following this doc: https://docs.airbyte.com/deploying-airbyte/on-kubernetes/

Hi! Thanks for the updates. Just to double check, were you following this doc: https://docs.airbyte.com/deploying-airbyte/on-kubernetes/

We've been using the helm chart

Ah, gotcha. This would be the correct doc then: https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm/#migration-from-old-chart-to-new-ones Were you following this while upgrading?

Ah, gotcha. This would be the correct doc then: https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm/#migration-from-old-chart-to-new-ones Were you following this while upgrading?

Hi @Nataly Merezhuk (Airbyte), Thanks for linking the migration guide, I'll look into this later and see if the minio configuration is the issue. Is the minio configuration related to the airbyte-worker deployment?

It looks like it is!