- Newest
- Most votes
- Most comments
Found the root cause. Looks like below are 2 mandatory requirements for this
- The location of the file in the DAG must be /usr/local/airflow/dags/kube_config.yaml
- Name of the kube config yaml must be kube_config.yaml
We specified s3 folder location in the DAG and it didn't pick up. Looks like MWAA mounts the dags folder in /usr/local/airflow. After fixing this, kube_config seems be to getting loaded.
Now we are running into below error [2023-01-26, 16:31:57 UTC] {{kubernetes_pod.py:675}} INFO - Building pod mwaa-pod-test-c7lcxfvu with labels: {'dag_id': 'kubernetes_pod_example', 'task_id': 'pod-task', 'run_id': 'manual__2023-01-26T163152.7629780000-7df477b2b', 'kubernetes_pod_operator': 'True', 'try_number': '1'} [2023-01-26, 16:31:57 UTC] {{kube_config.py:517}} ERROR - [Errno 13] Permission denied: 'aws-iam-authenticator' [2023-01-26, 16:31:57 UTC] {{kubernetes_pod.py:730}} ERROR - 'NoneType' object has no attribute 'metadata'
Do we need install aws-iam-authenticator in MWAA environment? If so, how to do that?
You need to allow inbound traffic in your EKS cluster security group from the MWAA environment security group.
Relevant content
- asked 2 years ago
- asked 3 years ago
- asked 2 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
You need to allow inbound traffic in your EKS cluster security group from the MWAA environment security group.