The GitHub Actions job "Tests (AMD)" on airflow.git/ramitkataria/eks-pod-identity has failed. Run started by GitHub user ramitkataria (triggered by ramitkataria).
Head commit for run: 39c4d4869d2e817cc817ff934259322913b97977 / Ramit Kataria <[email protected]> Eliminate trust policy race by migrating emr_eks test to Pod Identity The test shares one EMR job execution role across runs while each run creates its own EKS cluster. With IRSA, every run had to rewrite the shared role's trust policy to federate its own cluster's OIDC provider, and pruning old statements to stay under the trust policy size limit meant concurrent runs deleted each other's trust entries, failing jobs with AssumeRoleWithWebIdentity AccessDenied. IAM offers no compare-and-swap on trust policies, so this race cannot be fixed while runs mutate shared IAM state. EKS Pod Identity (supported by EMR on EKS since emr-7.3.0) removes the shared mutable state: the role keeps one static trust policy and each run creates Pod Identity associations scoped to its own cluster, also avoiding the 4096-char trust policy cap that limits IRSA to roughly a dozen clusters per role. Pod Identity is also AWS's recommended mechanism for pod credentials: > Unless you have specific usecases for IRSA, we recommend you use > EKS Pod Identities when using EKS. https://docs.aws.amazon.com/eks/latest/best-practices/identity-and-access-management.html#_eks_pod_identities_compared_to_irsa Report URL: https://github.com/apache/airflow/actions/runs/31051278951 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
