can I run multiple airbytes on the same external database server?

Running multiple Airbyte instances on the same external database server is not recommended. Each Airbyte instance should have its own dedicated database. This is because if you try to use the same database for different Airbyte deployments, it can lead to conflicts with Temporal internal databases. However, if you want to run multiple instances of Airbyte, you can consider using Restack, which makes it easier to deploy multiple instances of Airbyte on the same or multiple clusters. This way, you can test the latest version before upgrading or have a dedicated instance for development and for production. Here is an example of how to create a Kubernetes secret to store the database password for an Airbyte instance:

yaml apiVersion: v1   kind: Secret   metadata:     name: db-secrets   type: Opaque   stringData:     DATABASE_PASSWORD: <PASSWORD>

You can then run

kubectl apply -f db-secrets.yaml -n <NAMESPACE>

to create the secret in the namespace you're using Airbyte. Sources: - [Deploy Airbyte on Kubernetes using Helm](https://docs.airbyte.io/deploying-airbyte/on-kubernetes-via-helm#external-airbyte-database) - [Deploy multiple instances of Airbyte](https://docs.airbyte.io/deploying-airbyte/on-restack#deploy-multiple-instances-of-airbyte) - [Discussion on running multiple Airbyte instances](https://github.com/airbytehq/airbyte/discussions/28588)