This is an automated email from the ASF dual-hosted git repository.
jedcunningham 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 aae9b93383 Chart: minor clarifications to docs (#24929)
aae9b93383 is described below
commit aae9b9338372ac122dc38f9ee9589a1a7bc87cf5
Author: Aakcht <[email protected]>
AuthorDate: Sat Jul 9 07:14:07 2022 +0300
Chart: minor clarifications to docs (#24929)
---
docs/helm-chart/index.rst | 3 +++
docs/helm-chart/production-guide.rst | 2 +-
docs/helm-chart/setting-resources-for-containers.rst | 1 +
docs/helm-chart/using-additional-containers.rst | 4 ++--
4 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/docs/helm-chart/index.rst b/docs/helm-chart/index.rst
index e7660e61db..2bdf51a81e 100644
--- a/docs/helm-chart/index.rst
+++ b/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
-----------------------------------------
diff --git a/docs/helm-chart/production-guide.rst
b/docs/helm-chart/production-guide.rst
index b3cc556892..591217ac69 100644
--- a/docs/helm-chart/production-guide.rst
+++ b/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+ sc [...]
PgBouncer
---------
diff --git a/docs/helm-chart/setting-resources-for-containers.rst
b/docs/helm-chart/setting-resources-for-containers.rst
index 1261c9907f..4bfafc07e8 100644
--- a/docs/helm-chart/setting-resources-for-containers.rst
+++ b/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:
diff --git a/docs/helm-chart/using-additional-containers.rst
b/docs/helm-chart/using-additional-containers.rst
index 0cc1dd8353..4c3b6d6f82 100644
--- a/docs/helm-chart/using-additional-containers.rst
+++ b/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:
