For production environments, Whether to host the PostgreSQL metadata database separately or as a Kubernetes pod. What is recommended ?

[michaelkovatt]

Hi Team,

As of now superset ships Postgres database as part of Kubernetes setup as a separate Kubernetes POD that hosts the Postgres database to store all metadata related information (charts, dashboards, roles etc.). Currently, when we configure Apache superset there is a dedicated POD exclusively hosting Postgres.

In a production setup, Is it better to host the Postgres metadata database (Managed setup) separately ?. Or is it fine to keep it as a Kubernetes POD itself ?

What is the best practice and recommendation from superset team ?

Current setup, where we have a seperate postgres sql pod hosting postgres db. Example below:

[nytai]

the k8s pod is only included as a convenience feature to allow you to bring up superset with a k8s cluster and a few commands. Using a dedicated database service for postgres is generally recommended

[michaelkovatt]

thank you @nytai.