You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have an issue with the role assumed by my pod. If I check the AWS_ROLE_ARN value it has the right profile but when doing aws sts get-caller-identity from the pod it shows the NODE role and not the one linked to the ServiceAccount.
Values seem to be well set by the AddOn:
env:
AWS_STS_REGIONAL_ENDPOINTS: regional
AWS_ROLE_ARN: arn:aws:iam::...:role/...
AWS_WEB_IDENTITY_TOKEN_FILE: /var/run/secrets/eks.amazonaws.com/serviceaccount/token
Mounts:
/var/run/secrets/eks.amazonaws.com/serviceaccount from aws-iam-token (ro)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-wjbpg (ro)
Volumes:
aws-iam-token:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 86400
kube-api-access-wjbpg:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
I saw that when I describe the ServiceAccount, a few values are , can it be an issue ?
Hi,
I have an issue with the role assumed by my pod. If I check the
AWS_ROLE_ARN
value it has the right profile but when doingaws sts get-caller-identity
from the pod it shows the NODE role and not the one linked to theServiceAccount
.Values seem to be well set by the AddOn:
I saw that when I describe the ServiceAccount, a few values are , can it be an issue ?
I've rechecked the steps in https://docs.aws.amazon.com/eks/latest/userguide/associate-service-account-role.html#irsa-confirm-role-configuration but everything seems to be done like stated in this doc.
Environment:
eu-west-3
aws eks describe-cluster --name <name> --query cluster.platformVersion
):eks.2
aws eks describe-cluster --name <name> --query cluster.version
):1.30
v1.2.0-eksbuild.1
Am I missing something ?
Thanks !
The text was updated successfully, but these errors were encountered: