pod not using the role defined on the ServiceAccount (IRSA) rather default to node role

ForgeRock / secret-agent

Generate random Kubernetes secrets and optionally store them in a Cloud Secret Manager

Apache License 2.0

17 stars 20 forks source link

pod not using the role defined on the ServiceAccount (IRSA) rather default to node role #264

Open kamit78 opened 7 months ago

kamit78 commented 7 months ago

Hi, We are using secret agent operator (v1.1.6) with AWS EKS to manage and synchronize all secrets

Right now secret agent operator not using IRSA role defined in service account rather default to node(EC2) role. Integration works on assigning permissions to node role.

Is it a known issue in this version? or I'm missing something

Regards, Amit Kumar

balpurewal commented 6 months ago

This is fixed in the latest version 1.2.2, us-docker.pkg.dev/forgeops-public/images/secret-agent:v1.2.2