admin管理员组

文章数量:1312642

Looking for help on using the EKSPodOperator. My set up is as follows: Airflow Version: 2.6.2 deployed with the official helm chart v1.15.0 Kubernetes Cluster: EKS 1.30 Executor: LocalExecutor Postgres Database is accessed through AWS secrets backend connection.

My intention is to authenticate to the cluster through the scheduler's service account which has been annotated with the appropriate IAM role and policies.

Issue When I triggered the DAGs, I got a permission error relating to kubernetes_default and aws_default secrets which I didn't even create in the first place. To get past this, I granted the permission to the Scheduler's IAM role, and also created both secrets with the following content to facilitate the connection:

kubernetes_default: kubernetes://?extra__kubernetes__namespace=airflow&extra__kubernetes__in_cluster=True
aws_default: aws://?region_name=eu-west-1

Result: "ERROR - Invalid connection configuration. Options kube_config_path, kube_config, in_cluster are mutually exclusive. You can only use one option at a time. I do not have kube_config_path and kube_config set anywhere.

If I set in_cluster to false, I get the error - 'NoneType' object has no attribute 'metadata'. I get the same errors when I delete the secrets just in case they are causing some sort of conflict.

My preference is to use the in_cluster configuration since the tasks will be executed within the cluster and I'd like to use a service account for authentication.

Has anyone successfully used EKSPodOperator with in-cluster auth on EKS? What steps did you follow? Any help or guide will be much appreciated. Thank you.

本文标签：

版权声明：本文标题：amazon web services - How do I use the EKSPodOperator with in_cluster set to True with a ServiceAccount without getting an Error 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1741916652a2404774.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。