Chart: add small clarifications to docs

docs/helm-chart/index.rst

@@ -119,6 +119,9 @@ To uninstall/delete the ``airflow`` deployment:
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
 
+.. note::
+  Some kubernetes resources created by the chart `helm hooks <https://helm.sh/docs/topics/charts_hooks/#hook-resources-are-not-managed-with-corresponding-releases>`__ might be left in the namespace after executing ``helm uninstall``, for example, ``brokerUrlSecret`` or ``fernetKeySecret``.
+
 Installing the Chart with Argo CD or Flux
 -----------------------------------------
 

docs/helm-chart/production-guide.rst

@@ -59,7 +59,7 @@ configure the secret name:
 .. _production-guide:pgbouncer:
 
 .. warning::
-  If you use ``CeleryExecutor``, keep in mind that ``resultBackendSecretName`` expects a url that starts with ``db+postgresql://``, while ``metadataSecretName`` expects ``postgresql://`` and won't work with ``db+postgresql://``. You'll need to create separate secrets with the correct scheme.
+  If you use ``CeleryExecutor`` and Airflow version < ``2.4``, keep in mind that ``resultBackendSecretName`` expects a url that starts with ``db+postgresql://``, while ``metadataSecretName`` expects ``postgresql://`` and won't work with ``db+postgresql://``. You'll need to create separate secrets with the correct scheme. For Airflow version >= ``2.4`` it is possible to omit the result backend secret, as Airflow will use ``sql_alchemy_conn`` (specified in ``metadataSecret``) with a db+ scheme prefix by default.
 
 PgBouncer
 ---------

docs/helm-chart/setting-resources-for-containers.rst

@@ -35,6 +35,7 @@ Possible Containers where resources can be configured include:
    * ``dags.gitSync.resources``
    * ``webserver.resources``
    * ``flower.resources``
+   * ``dagProcessor.resources``
    * ``triggerer.resources``
 
 * Containers used for Airflow k8s jobs or cron jobs. You can add the resources for these Containers through the following parameters:

docs/helm-chart/using-additional-containers.rst

@@ -22,7 +22,7 @@ Sidecar Containers
 ------------------
 
 If you want to deploy your own sidecar container, you can add it through the ``extraContainers`` parameter.
-You can define different containers for the scheduler, webserver, worker, triggerer, flower, create user Job and migrate database Job Pods.
+You can define different containers for the scheduler, webserver, worker, triggerer, DAG processor, flower, create user Job and migrate database Job Pods.
 
 For example, sidecars that sync DAGs from object storage.
 
@@ -49,7 +49,7 @@ Init Containers
 ---------------
 
 You can also deploy extra init containers through the ``extraInitContainers`` parameter.
-You can define different containers for the scheduler, webserver, worker and triggerer pods.
+You can define different containers for the scheduler, webserver, worker, triggerer and DAG processor pods.
 
 For example, an init container that just says hello: