You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: chart/docs/using-additional-containers.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ Init Containers
52
52
---------------
53
53
54
54
You can also deploy extra init containers through the ``extraInitContainers`` parameter.
55
-
You can define different containers for the scheduler, webserver, apiserver, worker, triggerer, dag processor, create user job and migrate database job pods.
55
+
You can define different containers for the scheduler, webserver/api-server, Celery/Kubernetes workers, triggerer, dag processor, create user job and migrate database job pods.
56
56
57
57
For example, an init container that just says hello:
``workers.extraInitContainers`` field is now deprecated in favor of ``workers.celery.extraInitContainers`` and ``workers.kubernetes.extraInitContainers``. Please update your configuration accordingly.
Copy file name to clipboardExpand all lines: chart/values.schema.json
+17-1Lines changed: 17 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2301,7 +2301,7 @@
2301
2301
}
2302
2302
},
2303
2303
"extraInitContainers": {
2304
-
"description": "Add additional init containers into Airflow Celery workers and pods created with pod-template-file (templated).",
2304
+
"description": "Add additional init containers into Airflow Celery workers and pods created with pod-template-file (templated) (deprecated, use ``workers.celery.extraInitContainers`` and/or ``workers.kubernetes.extraInitContainers`` instead).",
0 commit comments