From 19ce6019f57d35c438e1adc361366381ba6d1415 Mon Sep 17 00:00:00 2001 From: marcosmarxm Date: Mon, 5 Feb 2024 13:52:35 -0300 Subject: [PATCH] update doc pg13 requirement for external db --- docs/enterprise-setup/implementation-guide.md | 4 ++++ docs/operator-guides/configuring-airbyte-db.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/docs/enterprise-setup/implementation-guide.md b/docs/enterprise-setup/implementation-guide.md index e01a4123d6743..60e20833bd930 100644 --- a/docs/enterprise-setup/implementation-guide.md +++ b/docs/enterprise-setup/implementation-guide.md @@ -105,6 +105,10 @@ To configure basic auth (deploy without SSO), remove the entire `auth:` section For Self-Managed Enterprise deployments, we recommend using a dedicated database instance for better reliability, and backups (such as AWS RDS or GCP Cloud SQL) instead of the default internal Postgres database (`airbyte/db`) that Airbyte spins up within the Kubernetes cluster. +:::info +Currently, Airbyte requires connection to a Postgres 13 instance. +::: + We assume in the following that you've already configured a Postgres instance:
diff --git a/docs/operator-guides/configuring-airbyte-db.md b/docs/operator-guides/configuring-airbyte-db.md index 899e86b01fed7..9adc4c881b568 100644 --- a/docs/operator-guides/configuring-airbyte-db.md +++ b/docs/operator-guides/configuring-airbyte-db.md @@ -25,6 +25,10 @@ If you need to interact with it, for example, to make back-ups or perform some c ## Connecting to an External Postgres database +:::info +Currently, Airbyte requires connection to a Postgres 13 instance. +::: + Let's walk through what is required to use a Postgres instance that is not managed by Airbyte. First, for the sake of the tutorial, we will run a new instance of Postgres in its own docker container with the command below. If you already have Postgres running elsewhere, you can skip this step and use the credentials for that in future steps. ```bash