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.
I was trying to use AWS parameter store as the backend for my airflow variables but nothing is getting sync. I am following the documentation on AWS Connection Option 3
I attempted to use two different roles, one with only access with the necessary permissions including the correct namespace and the one with total admin access to my EKS cluster. Nothing is getting synced which leads me to believe this may be a bug? I can't say for certain because there does not seem to be any logs indicating something went wrong and I have no idea where to look. All pods are running fine.
Using airflow config list I am getting the correct arguments
I have no way of validating that airflow is able to connect to AWS Parameter store. Any help would be greatly appreciated. Also these same configurations worked with helm chart 2.5.3 and airflow 2.2.3
Checks
User-Community Airflow Helm Chart
.Chart Version
8.8.0
Kubernetes Version
Helm Version
Description
Note, I am using airflow 2.7.3-python3.10
I was trying to use AWS parameter store as the backend for my airflow variables but nothing is getting sync. I am following the documentation on AWS Connection Option 3
I attempted to use two different roles, one with only access with the necessary permissions including the correct namespace and the one with total admin access to my EKS cluster. Nothing is getting synced which leads me to believe this may be a bug? I can't say for certain because there does not seem to be any logs indicating something went wrong and I have no idea where to look. All pods are running fine.
Using
airflow config list
I am getting the correct argumentsI have SSM vars that exist with the correct prefix
airflow/variables/test
butairflow variables list
shows nothingMy service account exist and has the correct annotations and all my pods are assigned to this service account
I have no way of validating that airflow is able to connect to AWS Parameter store. Any help would be greatly appreciated. Also these same configurations worked with helm chart 2.5.3 and airflow 2.2.3
Relevant Logs
Custom Helm Values