Error with Google Secret Manager in Airbyte deployment on Kubernetes using Helm

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

When trying to add a new source in Airbyte deployed on Kubernetes using Helm with Google Secret Manager, a secret is created but the system cannot locate it. Additionally, the workspace id is not set correctly.


Question

Hello! I am using Google Secret Manager when deploying Airbyte on Kubernetes using Helm and the access seems fine because when i try to add a new source, a secret is created on the Google Secret Manager, but it gives an error and i get the following log:
GoogleSecretManagerPersistence(read):63 - Unable to locate secret for coordinate airbyte_workspace_00000000-0000-0000-0000-000000000000_secret_78d24386-2896-4599-8fda-4cd37394b354_v1
Why can’it it find this secret even though it is created, and why does it not set the correct workspace id but it sets all 0s

This is my Helm values:

  secretsManager:
    type: googleSecretManager
    storageSecretName: airbyte-config-secrets
    googleSecretManager:
      projectId: PROJECT_ID
      credentialsSecretKey: gcp.json```

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1723709341957499) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["google-secret-manager", "kubernetes", "helm", "airbyte", "workspace-id", "error"]
</sub>