Skip to content
Discussion options

You must be logged in to vote

Yes, however it is not officially documented.
You shoud have working IAM role association for service accounts in your self-hosted cluster via AWS IAM OIDC (or similar approach like kube2iam, but I haven't tested it).
Then you should:

  1. Set driverWritesSecrets launch argument to True (currently not possible via Helm, but I am already on it)
  2. Create IAM role with permissions to sts:AssumeRoleWithWebIdentity (see the Medium article above) and secretsmanager:GetSecretValue.
  3. Add "eks.amazonaws.com/role-arn" annotation to the service account you will use later for your pod. Use ARN of the role from step 2 as the value.
  4. Add AWS_DEFAULT_REGION, AWS_ROLE_ARN, AWS_WEB_IDENTITY_TOKEN_FILE envs to you…

Replies: 5 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by jirkafajfr
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
bug Something isn't working
5 participants
Converted from issue

This discussion was converted from issue #335 on May 06, 2024 18:51.