在 Kubernetes 上安装 Apache Airflow 的 Helm 图表_Python_代码_下载

# Astronomer's Helm Chart for Apache Airflow This chart will bootstrap an [Airflow](https://github.com/astronomer/ap-airflow) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager. ## Quickstart To install this helm chart remotely (using helm 3) ```bash kubectl create namespace airflow helm repo add astronomer https://helm.astronomer.io helm install airflow --namespace airflow astronomer/airflow ``` To install airflow with the KEDA autoscaler ```bash helm repo add kedacore https://kedacore.github.io/charts helm repo add astronomer https://helm.astronomer.io helm repo update kubectl create namespace keda helm install keda \ --namespace keda kedacore/keda \ --version "v1.5.0" kubectl create namespace airflow helm install airflow \ --set executor=CeleryExecutor \ --set workers.keda.enabled=true \ --set workers.persistence.enabled=false \ --namespace airflow \ astronomer/airflow ``` To install this repository from source ```bash kubectl create namespace airflow helm install --namespace airflow . ``` ## Prerequisites - Kubernetes 1.12+ - Helm 3.6+ - PV provisioner support in the underlying infrastructure ## Installing the Chart To install the chart with the release name `my-release`: ```bash helm install --name my-release . ``` The command deploys Airflow on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation. > **Tip**: List all releases using `helm list` ## Upgrading the Chart First, look at the [updating documentation](UPDATING.md) to identify any backwards-incompatible changes. To upgrade the chart with the release name `my-release`: ```bash helm upgrade --name my-release . ``` ## Uninstalling the Chart To uninstall/delete the `my-release` deployment: ```bash helm delete my-release ``` The command removes all the Kubernetes components associated with the chart and deletes the release. ## Updating DAGs ### Bake DAGs in Docker image The recommended way to update your DAGs with this chart is to build a new docker image with the latest code (`docker build -t my-company/airflow:8a0da78 .`), push it to an accessible registry (`docker push my-company/airflow:8a0da78`), then update the Airflow pods with that image: ```bash helm upgrade my-release . \ --set images.airflow.repository=my-company/airflow \ --set images.airflow.tag=8a0da78 ``` ### Deploying DAGs using `git-sync` `extraContainers`, `extraInitContainers`, `extraVolumes`, and `extraVolumeMounts` can be combined to deploy git-sync. The following example relies on `emptyDir` volumes and works with `KubernetesExecutor`. ```yaml env: - name: AIRFLOW__CORE__DAGS_FOLDER value: /usr/local/airflow/dags/latest/airflow/example_dags scheduler: extraInitContainers: - name: init-gitsync image: k8s.gcr.io/git-sync/git-sync:v3.2.2 imagePullPolicy: IfNotPresent env: - name: GIT_SYNC_REPO value: https://github.com/apache/airflow.git - name: GIT_SYNC_ROOT value: /usr/local/airflow/dags - name: GIT_SYNC_DEST value: latest - name: GIT_SYNC_ONE_TIME value: "true" volumeMounts: - mountPath: /usr/local/airflow/dags name: dags readOnly: false extraContainers: - name: gitsync image: k8s.gcr.io/git-sync/git-sync:v3.2.2 imagePullPolicy: IfNotPresent env: - name: GIT_SYNC_REPO value: https://github.com/apache/airflow.git - name: GIT_SYNC_ROOT value: /usr/local/airflow/dags - name: GIT_SYNC_DEST value: latest - name: GIT_SYNC_WAIT value: "10" volumeMounts: - mountPath: /usr/local/airflow/dags name: dags readOnly: false extraVolumeMounts: - name: dags mountPath: /usr/local/airflow/dags extraVolumes: - name: dags emptyDir: {} workers: extraInitContainers: - name: gitsync image: k8s.gcr.io/git-sync/git-sync:v3.2.2 imagePullPolicy: IfNotPresent env: - name: GIT_SYNC_REPO value: https://github.com/apache/airflow.git - name: GIT_SYNC_ROOT value: /usr/local/airflow/dags - name: GIT_SYNC_DEST value: latest - name: GIT_SYNC_ONE_TIME value: "true" volumeMounts: - mountPath: /usr/local/airflow/dags name: dags readOnly: false extraVolumeMounts: - name: dags mountPath: /usr/local/airflow/dags extraVolumes: - name: dags emptyDir: {} ``` ## Docker Images - The Airflow image that are referenced as the default values in this chart are generated from this repository: https://github.com/astronomer/ap-airflow. - Other non-airflow images used in this chart are generated from this repository: https://github.com/astronomer/ap-vendor. ## Parameters The complete list of parameters supported by the community chart can be found on the [Parameteres Reference](https://airflow.apache.org/docs/helm-chart/stable/parameters-ref.html) page, and can be set under the `airflow` key in this chart. The following tables lists the configurable parameters of the Astronomer chart and their default values. | Parameter | Description | Default | | | :-------------------------------------------- | :-------------------------------------------------------------------------------------------------------- | :---------------------------- | :-- | | `ingress.enabled` | Enable Kubernetes Ingress support | `false` | | | `ingress.acme` | Add acme annotations to Ingress object | `false` | | | `ingress.tlsSecretName` | Name of secret that contains a TLS secret | `~` | | | `ingress.webserverAnnotations` | Annotations added to Webserver Ingress object | `{}` | | | `ingress.flowerAnnotations` | Annotations added to Flower Ingress object | `{}` | | | `ingress.baseDomain` | Base domain for VHOSTs | `~` | | | `ingress.auth.enabled` | Enable auth with Astronomer Platform | `true` | | | `workers.autoscaling.enabled` | Traditional HorizontalPodAutoscaler | `false` | | | `workers.autoscaling.minReplicas` | Minimum amount of workers | `1` | | | `workers.autoscaling.maxReplicas` | Maximum amount of workers | `10` | | | `workers.autoscaling.targetCPUUtilization` | Target CPU Utilization of workers | `80` | | | `workers.autoscaling.targetMemoryUtilization` | Target Memory Utilization of workers