You can do this using the following command: kubectl logs If you're still encountering issues, consider checking the logs of your Airflow pods for any error messages. Then, reference the Secret in your values.yaml file: imagePullSecrets:įor more detailed information on configuring your Airflow deployment with Helm, refer to the official Apache Airflow Helm Chart documentation. You can create the Secret using the following command: kubectl create secret docker-registry regcred -docker-server= -docker-username= -docker-password= -docker-email= If you're using a private Docker repository, you'll also need to create a Kubernetes Secret with your Docker registry credentials and reference it in your values.yaml file. Here's an example of how these parameters might be set in your values.yaml file: defaultAirflowRepository: apache/airflow If not defined for specific pods, the default values will be used. securit圜ontext: This defines the security settings for your Airflow pods.airflowVersion: This should match the version of Airflow you're deploying.defaultAirflowTag: This should be set to the tag of your Airflow image.defaultAirflowRepository: This should be set to the Docker repository of your Airflow image.Here are some key parameters you should check: This file is used by Helm, a package manager for Kubernetes, to customize the configuration of your Apache Airflow deployment. To resolve Airflow configuration issues when setting up a CI/CD pipeline with GitHub, you need to ensure that your Airflow settings are correctly configured in your values.yaml file.

Airflow docker run parameters