Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minimal Postgres Version Supported as External Database #48542

Open
marcosmarxm opened this issue Nov 18, 2024 · 3 comments
Open

Minimal Postgres Version Supported as External Database #48542

marcosmarxm opened this issue Nov 18, 2024 · 3 comments
Labels
area/documentation Improvements or additions to documentation area/platform issues related to the platform team/deployments type/bug Something isn't working

Comments

@marcosmarxm
Copy link
Member

marcosmarxm commented Nov 18, 2024

Helm Chart Version

What step the error happened?

Other

Relevant information

The documentation External Database do not inform users what is the minimal and maximum version supported. This can cause confusion to users.

Also can be good information to include in the values.yaml file.

Relevant log output

@marcosmarxm marcosmarxm added area/platform issues related to the platform needs-triage team/deployments type/bug Something isn't working area/documentation Improvements or additions to documentation and removed needs-triage labels Nov 18, 2024
@joeybenamy
Copy link

This would be helpful for us. We are looking for info on Postgres 17 support.

@PrestonBlackburn
Copy link

I did some minimal testing with various Postgres versions on AWS RDS for the external database. Here are the results:

Postgres Version Test Status
12.19 Passed
13.15 Passed
14.12 Passed
15.7 Passed
16.3 Passed
17.1 Passed

For the tests, I just checked to see if the helm chart would deploy and then if I could create an connect a Snowflake destination.

Setup:

Helm Chart Version: 1.3.0

values.yaml
(just the changes)

postgresql:
  enabled: false

global:
  database:
    type: "external"
    secretName: "airbyte-config-secrets"
    host: "<rds db name>.<rds id>.<rds region>.rds.amazonaws.com"
    port: "5432"
    database: "airbyte"
    userSecretKey: "database-user"
    passwordSecretKey: "database-password"

secrets.yaml

apiVersion: v1
kind: Secret
metadata:
  name: airbyte-config-secrets

type: Opaque
stringData:
  database-user: postgres
  database-password: my_password

Note
Sometimes the helm install command would fail - and it seems like it was due to timeout issues, since if I ran the command again it would succeeed. I'd recommend increasing the timeout if you run into this issue, ex:

helm install release-1 airbyte/airbyte -f values.yaml --timeout 10m0s

I also needed to create the Airbyte databases before deploying the helm charts

CREATE DATABASE airbyte WITH OWNER = postgres;
CREATE DATABASE temporal WITH OWNER = postgres;
CREATE DATABASE temporal_visibility WITH OWNER = postgres;

@joeybenamy
Copy link

I did some minimal testing with various Postgres versions on AWS RDS for the external database. Here are the results:

Postgres Version Test Status
12.19 Passed
13.15 Passed
14.12 Passed
15.7 Passed
16.3 Passed
17.1 Passed
For the tests, I just checked to see if the helm chart would deploy and then if I could create an connect a Snowflake destination.

Setup:

Helm Chart Version: 1.3.0

values.yaml (just the changes)

postgresql:
enabled: false

global:
database:
type: "external"
secretName: "airbyte-config-secrets"
host: "...rds.amazonaws.com"
port: "5432"
database: "airbyte"
userSecretKey: "database-user"
passwordSecretKey: "database-password"
secrets.yaml

apiVersion: v1
kind: Secret
metadata:
name: airbyte-config-secrets

type: Opaque
stringData:
database-user: postgres
database-password: my_password
Note Sometimes the helm install command would fail - and it seems like it was due to timeout issues, since if I ran the command again it would succeeed. I'd recommend increasing the timeout if you run into this issue, ex:

helm install release-1 airbyte/airbyte -f values.yaml --timeout 10m0s
I also needed to create the Airbyte databases before deploying the helm charts

CREATE DATABASE airbyte WITH OWNER = postgres;
CREATE DATABASE temporal WITH OWNER = postgres;
CREATE DATABASE temporal_visibility WITH OWNER = postgres;

This is very helpful for us as we start planning our upgrade to Postgres 17.x. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Improvements or additions to documentation area/platform issues related to the platform team/deployments type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants