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

eks: make aws-auth ConfigMap future compatible #2707

Merged
merged 2 commits into from
Feb 7, 2020

Conversation

bonifaido
Copy link
Member

@bonifaido bonifaido commented Feb 7, 2020

Signed-off-by: Nandor Kracser [email protected]

Q A
Bug fix? no
New feature? no
API breaks? no
Deprecations? no
Related tickets kubernetes-sigs/aws-iam-authenticator#268, #2699
License Apache 2.0

What's in this PR?

Why?

The aws-iam-authenticator doesn't handle path currently in role mappings: kubernetes-sigs/aws-iam-authenticator#268
Once this bug gets fixed our code won't work, so we are making it future compatible by adding the role id with and without a path to the mapping. Since IAM role IDs are unique within an account this is not a security concern.

Additional context

Checklist

  • Implementation tested (with at least one cloud provider)

@bonifaido bonifaido self-assigned this Feb 7, 2020
@bonifaido bonifaido added the distribution/eks Amazon EKS label Feb 7, 2020
@bonifaido bonifaido force-pushed the eks-mapRoles-future-proof branch from 3afb67f to 7186520 Compare February 7, 2020 13:09
@bonifaido bonifaido merged commit f712b54 into master Feb 7, 2020
@bonifaido bonifaido deleted the eks-mapRoles-future-proof branch February 7, 2020 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants