This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new b7d32d7cf5 Add more explicit "embedded postgres" exclusion for 
production (#33034)
b7d32d7cf5 is described below

commit b7d32d7cf54346a86cd0d1f50b8157ea2febeee1
Author: Jarek Potiuk <[email protected]>
AuthorDate: Wed Aug 2 14:37:56 2023 +0200

    Add more explicit "embedded postgres" exclusion for production (#33034)
    
    Our language that warned about not using the embedded postgres for
    production in our Helm Chart was not strong enough. It only "advised"
    to use external database, but really the embedded Postgres lacks
    all the the things that you need when you want to make sure your
    production deployment is "safe" - persistency, monitoring, backup,
    upgrade scenarios are all missing.
    
    I think we should be much stronger in saying "data loss might occur"
    "you SHOULD NOT" use it for production. This is much more realistic
    warning and it makes it easier for us to direct users who have
    problems with embedded postgres to use "real" database for production.
---
 docs/helm-chart/production-guide.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/helm-chart/production-guide.rst 
b/docs/helm-chart/production-guide.rst
index 1f5a9032d8..6451205611 100644
--- a/docs/helm-chart/production-guide.rst
+++ b/docs/helm-chart/production-guide.rst
@@ -25,8 +25,10 @@ Database
 
 It is advised to set up an external database for the Airflow metastore. The 
default Helm chart deploys a
 Postgres database running in a container. For production usage, a database 
running on a dedicated machine or
-leveraging a cloud provider's database service such as AWS RDS is advised. 
Supported databases and versions
-can be found at :doc:`Set up a Database Backend 
<apache-airflow:howto/set-up-database>`.
+leveraging a cloud provider's database service such as AWS RDS should be used 
because the embedded Postgres
+lacks stability, monitoring and persistence features that you need for a 
production database. It is only there to
+make it easier to test the Helm Chart in a "standalone" version but you might 
experience data loss when you
+are using it. Supported databases and versions can be found at :doc:`Set up a 
Database Backend <apache-airflow:howto/set-up-database>`.
 
 
 .. note::

Reply via email to