Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add podAnnotations: #262

Open
jmturwy opened this issue Apr 15, 2020 · 2 comments
Open

add podAnnotations: #262

jmturwy opened this issue Apr 15, 2020 · 2 comments
Labels
chart Area: helm chart enhancement New feature or request

Comments

@jmturwy
Copy link

jmturwy commented Apr 15, 2020

I'd love to use my kiam and AWS roles to auto-unseal with the chart. this would allow my pod to use my aws role instead of using IAM user client and secrets

Example:
podAnnotations:
iam.amazonaws.com/role: k8s_vault

@pcman312 pcman312 added chart Area: helm chart enhancement New feature or request labels Apr 15, 2020
@silverbp
Copy link

silverbp commented May 21, 2020

you can add the annotation to the service account via this..

  serviceAccount:
    annotations:
      |
      "eks.amazonaws.com/role-arn": "${aws_role_arn}"

but it doesn't work, I don't think it has to do with the helm chart, I don't think the vault docker image is reading the environment variables and the token that are getting injected, cause when I do the above, I get the proper environment variables set, but vault errors out (no access) because it's using the node arn role when it should be using the arn that's assigned above.

@silverbp
Copy link

If you do something like this.. in the pod ahead of time..
aws/aws-cli#4477

I assume this will work..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chart Area: helm chart enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants