If true, it creates ClusterRole/ ClusterRolebinding (with access to entire cluster) Whether Airflow can launch workers and/or pods in multiple namespaces. Subpath within the PVC where dags are located.Ĭonnection : host : '.' pass : '.' port : '.' scheme : https user : '.'Ī secret containing the connection string.ĮnableBuiltInSecretEnvVars.AIRFLOW_CONN_AIRFLOW_DBĮnable AIRFLOW_CONN_AIRFLOW_DB variable to be read from the Metadata SecretĮnableBuiltInSecretEnvVars.AIRFLOW_CELERY_BROKER_URLĮnable AIRFLOW_CELERY_BROKER_URL variable to be read from the Celery Broker URL SecretĮnableBuiltInSecretEnvVars.AIRFLOW_CELERY_CELERY_RESULT_BACKENDĮnable AIRFLOW_CELERY_CELERY_RESULT_BACKEND variable to be read from the Celery Result Backend Secret - Airflow 1.10.* variantĮnableBuiltInSecretEnvVars.AIRFLOW_CELERY_RESULT_BACKENDĮnable AIRFLOW_CELERY_RESULT_BACKEND variable to be read from the Celery Result Backend SecretĮnableBuiltInSecretEnvVars.AIRFLOW_CORE_FERNET_KEYĮnable AIRFLOW_CORE_FERNET_KEY variable to be read from the Fernet key SecretĮnableBuiltInSecretEnvVars.AIRFLOW_CORE_SQL_ALCHEMY_CONNĮnable AIRFLOW_CORE_SQL_ALCHEMY_CONN variable to be read from the Metadata SecretĮnableBuiltInSecretEnvVars.AIRFLOW_DATABASE_SQL_ALCHEMY_CONNĮnable AIRFLOW_DATABASE_SQL_ALCHEMY_CONN variable to be read from the Metadata SecretĮnableBuiltInSecretEnvVars.AIRFLOW_ELASTICSEARCH_ELASTICSEARCH_HOSTĮnable AIRFLOW_ELASTICSEARCH_ELASTICSEARCH_HOST variable to be read from the Elasticsearch Host Secret - Airflow <1.10.4 variantĮnableBuiltInSecretEnvVars.AIRFLOW_ELASTICSEARCH_HOSTĮnable AIRFLOW_ELASTICSEARCH_HOST variable to be read from the Elasticsearch Host SecretĮnableBuiltInSecretEnvVars.AIRFLOW_WEBSERVER_SECRET_KEYĮnable AIRFLOW_WEBSERVER_SECRET_KEY variable to be read from the Webserver Secret Key SecretĮnvironment variables for all Airflow containers.ĮxtraEnvFrom : |- secretRef: name: '-airflow-variables'Įnable persistent volume for storing logs. If using a custom StorageClass, pass name here. Low values cause more traffic to the remote git repository.Įnable persistent volume for storing dags. High values are more likely to cause DAGs to become out of sync between different components. Interval between git sync attempts in seconds. Git sync container run as user parameter. Subpath within the repo where dags are located. Name of a Secret containing the repo sshKeySecret. Securit圜ontext : runAsGroup : 0 runAsUser : 50000 You can bake a webserver_config.py in to your image instead or specify a configmap containing the webserver_config.py. This string (can be templated) will be mounted into the Airflow webserver as a custom webserver_config.py. The Fernet key used to encrypt passwords (can only be set during install, not upgrade). Overrides tag.ĭefault airflow repository. Settings to go into the mounted airflow.cfgĭefault airflow digest to deploy. Is this a design mistake? I think this should be changed to allow for the intuitive behavior of setting a default toleration for the entire chart and then allowing specific parts to override that.Airflow_local_settings file as a string (can be templated).Īirflow version (Used to make some decisions based on Airflow Version being deployed). Values.tolerations), instead of allowing the second one (. It is using the Helm or operator, which I think takes the first not-null value (. The problem is, when I look at the actual template here, When setting the tolerations, I assumed that the best way to go was to set a “default” toleration for the whole chart (to the “core” pool), and override/extend that in the workers section to specify a different toleration. I am trying to get all the pods in the Chart to run on a specific node pool by using taints and tolerations, and the workers should run in a different (larger) pool. # want another toleration for only workers to only use the "worker" pool # tolerations for entire chart - use the "core" pool MetadataSecretName: airflow-db-creds-secret Here are the relevant parts: executor: "KubernetesExecutor" 1.3.0 (latest released) Apache Airflow versionġ.19.14-gke.1900 Helm Chart configuration
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |