-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Note
This issue is imported from the original repository: airflow-helm#104
Currently we use an init-container for all the *. extraPipPackages values, which must run every time the Pod starts.
This issue is worst for the airflow.kubernetesPodTemplate.extraPipPackages value, (which is related to the pod_template.yaml generation), as it means that users are installing those packages for literally EVERY TASK in thier DAGs.
I believe it would be possible to optionally allow the usage of a PVC rather than ephemeral volume, which would mean that pip-install only runs one-time per helm upgrade/install through the use of pre-install helm-hook Jobs.
(NOTE: it needs to be PRE-install because the user might install something like python-ldap for their webserver to be able to start)