Hi together and @kapa.ai, I deployed airbyte in an EKS and setup the parameter for the secretmanager to true and use aws secrets manager. When trying to connect to a an oracle database the secret is written to aws secrets manager but afterwards I receive the following error:

HikariPool-1 - Connection is not available, request timed out after 60001ms (total=0, active=0, idle=0, waiting=0)

and the following logs can be seen in the pod

Secret airbyte_workspace_000...000_secret_279396db-4ab-39e-ab65-dccclf6fdb8 v1 not found

Secret airbyte_workspace_000...000_secret_279396db-4ab-39e-ab65-dccclf6fdb8 not found.

Has anyone an idea what could be the issue here.

Sorry @Pascal Pfäffle, I'm not enabled for this channel yet. Please contact your workspace admins to help get me set up. 👋

Hi Pascal, thanks for reaching out. Can you check that the workload pod that has the init container has a similar AWS secrets manager configuration as the server pod? My hypothesis is that the server pod was able to write the secret to AWS but the init container isn't getting hydrated with the secret value.