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

Docs: update pg13 requirement for external db #34858

Merged
merged 1 commit into from
Feb 5, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/enterprise-setup/implementation-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:

<details>
Expand Down
4 changes: 4 additions & 0 deletions docs/operator-guides/configuring-airbyte-db.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading