airflow-helm / charts

The User-Community Airflow Helm Chart is the standard way to deploy Apache Airflow on Kubernetes with Helm. Originally created in 2017, it has since helped thousands of companies create production-ready deployments of Airflow on Kubernetes.
https://github.com/airflow-helm/charts/tree/main/charts/airflow
Apache License 2.0
663 stars 475 forks source link

cant set HTTP_PROXY in `airflow.extraPipPackages` init-container #322

Closed SingularBunny closed 3 years ago

SingularBunny commented 3 years ago

You have incorrect helper airflow.init_container.install_pip_packages. When it initializes, it doesn't contain airflow-config secret. Because of that many pods stuck if you use a proxy.

You need to add:

  envFrom:
    {{- include "airflow.envFrom" . | indent 4 }}
  env:
    {{- include "airflow.env" . | indent 4 }}

inside.

I am using version 8.4.1 of chart

Kubernetes Version: v1.21.3 Helm version: v3.6.3

Values:

airflow:

extraEnv:

web: extraPipPackages:

logs: persistence: enabled: true existingClaim: airflow-logs-claim

dags: initContainer: enabled: false installRequirements: true

persistence: enabled: true existingClaim: airflow-dags-claim

postgresql: enabled: false

externalDatabase: host: postgresql.postgresql.svc.cluster.local database: airflow_production user: airflow passwordSecret: postgresql-password

redis: enabled: false

externalRedis: host: redis-master.redis.svc.cluster.local passwordSecret: redis-password

thesuperzapper commented 3 years ago

@SingularBunny thanks for raising this, I have created https://github.com/airflow-helm/charts/issues/324 which describes what I plan to do.

thesuperzapper commented 3 years ago

@SingularBunny this feature will be available in version 8.5.0 of the chart (to be released today/tomorrow) because of PR: https://github.com/airflow-helm/charts/pull/365

__You can now set the HTTP_PROXY configs in airflow.config, for example:__

airflow:
  config:
    HTTP_PROXY: http://example.com:8080

  extraPipPackages:
    - "xxxxxx==1.0.0"