sudeepgupta90 commented on code in PR #29078: URL: https://github.com/apache/airflow/pull/29078#discussion_r1083432489
########## docs/helm-chart/index.rst: ########## @@ -140,3 +140,22 @@ will not start as the migrations will not be run: This is so these CI/CD services can perform updates without issues and preserve the immutability of Kubernetes Job manifests. This also applies if you install the chart using ``--wait`` in your ``helm install`` command. + +.. note:: + While deploying this Helm chart with Argo, you might encounter issues with database migrations not running automatically on upgrade. + +To ensure database migrations with Argo CD, you will need to add: + +.. code-block::yaml + + migrateDatabaseJob: + jobAnnotations: + "argocd.argoproj.io/hook": Sync + +and, equivalent configurations in case of Flux CD + +.. note:: + This will ensure database migrations run when the Airflow Docker image is upgraded. This approach has a limitation in that the database migrations will run every time there is a ``Sync`` event in Argo. This is a trade-off for automation at the cost of some computational loss. + +.. warning:: + While deploying with Argo CD, you may encounter issues with (built-in) Redis secrets (when you use the Celery(Kubernetes)Executor) not being rotated properly after Airflow pods restart. It's recommended that you bring your own Redis. See `Celery Backend <production-guide#celery-backend>`__ Review Comment: I will make this change -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
