Issue with Helm deployment when specifying custom database values.yml

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

Summary

The user is experiencing timeouts during Helm deployment when specifying a custom database in the values.yml file. The provided values.yml file includes configurations for an external database and a secret, but there may be errors causing the timeout.


Question

We try to deploy from Helm to our K8s. It works fine if we don’t specify a values.yml. But if i specify a values.yml for a custom database it times out on the Helm deploy. Any obvious errors with the below values.yml file please?

  # Change the value from true to false.
  enabled: false
externalDatabase:
  # Add the host, username and database name you're using.
  host: ds-postgres-service
  user: postgres
  database: postgres
  password: ""
  existingSecret: "db-secrets"
  existingSecretPasswordKey: "DATABASE_PASSWORD"
  port: 5432
  jdbcUrl: ""
global:
  database:
    secretName: "db-secrets"
    secretValue: "DATABASE_PASSWORD"
    host: ds-postgres-service
    port: 5432
    database: postgres```
```apiVersion: v1
kind: Secret
metadata:
  name: db-secrets
type: Opaque
stringData:
  DATABASE_PASSWORD: password```

<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/p1718128956160739) if you want 
to access the original thread.

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

<sub>
["helm-deployment", "custom-database", "values.yml", "timeout", "postgresql", "externalDatabase", "global", "secret", "kubernetes"]
</sub>