Delegates running in Amazon EKS Pod Identity
pending feedback
Y
Yellow sunshine Badger
We're trying to use the AWS Pod Identity association feature in AWS EKS, but it doesn't seem to be working. Could you please enable support for this feature?
Log In
S
Saffron Dormouse
+1 on this feature. Per this article(https://medium.com/@sanathw/is-irsa-obsolete-eks-pod-identity-quietly-rewrote-iam-for-kubernetes-9cf686567ad0), while IRSA is not going away for EKS, "Pod Identiy is the cleaner, safer, future proof choice", and our company is moving in that direction, so this would be a valuable feature.
O
Olive green Opossum
+1 on this feature, Pod Identities have several advantages over IRSA.
Pod Identities seem to work fine in CI workloads that are reliant on the infrastructure identity (i.e. running
aws sts assume-role ...
directly in a step), but it doesn't work in Harness AWS ConnectorsIt's worth noting that existing connectors (that make use of cross account IRSA) should work out of the box when Pod Identities are supported. Otherwise customers might need to update hundreds of existing connectors.
S
Spatial Bandicoot
+1 for this feature. If AWS is moving away from IRSA, it makes sense for end users and customers to do the same.
Y
Yellow sunshine Badger
Rohan Gupta yup! we currently use IRSA for Harness and have been for quite a while, but we would love to move over to pod identity to match the rest of our infra
the UX of pod identity is greatly preferred over IRSA
Rohan Gupta
marked this post as
pending feedback
Rohan Gupta
Did you follow the documentation for IRSA? That is what a majority of our users leverage today. https://developer.harness.io/docs/platform/connectors/cloud-providers/add-aws-connector/#use-irsa
The Pod Identity feature auth alone is not supported. You can use it in conjunction with IRSA. The connector will operate based of the IRSA configuration.