Optionally return full role arn including path during token verification

[terricain]

What this PR does / why we need it: When creating EKS nodegroups where the node's IAM role contains a path, the nodes fail to join the cluster. This adds the ability to look up a role's full ARN including the path and return that when verifying a token.

The reason this is needed is because the assume-role ARN that is returned by sts.get-caller-idendentity does not include the IAM role's path.

I've added a "role cache" which calles iam.list-roles and stores a mapping between the roles unique role ID and the full ARN, as the UserID returned by sts.get-caller-identity contains the roles unique ID therefore looking up the existing role's correct ARN is possible.

This does require the clusters IAM role to have the iam:ListRoles action. If the role cache gets an error when calling list roles and its not a transient error, it'll disable all future lookups and the functionality will revert to the original behaviour. I figured it would be better to make this more an opt in rather than a requirement as else it might just break nodes joining a cluster whenever its released.

Which issue(s) this PR fixes: Fixes #268 Fixes #153

[linux-foundation-easycla[bot]]

The committers listed above are authorized under a signed CLA.

• :white_check_mark: login: terrycain / name: Terry Cain (885868b77349c3c1a0a790e9e444cf8ae8c5453a)

[k8s-ci-robot]

Welcome @terrycain!

It looks like this is your first PR to kubernetes-sigs/aws-iam-authenticator 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-iam-authenticator has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. :smiley:

[k8s-ci-robot]

Hi @terrycain. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: terrycain Once this PR has been reviewed and has the lgtm label, please assign jyotimahapatra for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[terricain]

@dims / @nckturner / @nnmin-aws can we get a review on this please?

[nnmin-aws]

/test

[k8s-ci-robot]

@nnmin-aws: The /test command needs one or more targets. The following commands are available to trigger required jobs:

• /test pull-aws-iam-authenticator-e2e
• /test pull-aws-iam-authenticator-e2e-kind
• /test pull-aws-iam-authenticator-integration
• /test pull-aws-iam-authenticator-unit

Use /test all to run all jobs.

In response to this:

/test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nnmin-aws]

/test all

[terricain]

Thanks @nnmin-aws the tests seem to have passed, what now?

[terricain]

@nnmin-aws @dims @nckturner what else is required for this PR? There's been no progress for nearly 2 months, some guidance would be appreciated.

[dims]

cc @cartermckinnon

[nnmin-aws]

@terrycain @dims apology for the delay! i am so sorry about it. We were hesitating at the change because it requires additional invocation of aws IAM and might increase latency of authN.

There is another PR actually merged https://github.com/kubernetes-sigs/aws-iam-authenticator/pull/670/files#diff-5de38ab8d77d935766314beeb9a9e3b7165eb470e656dbb5e4fdf9bb60ae59de. which removed the path from the arn comparison.

Could you please kindly pull latest release and verify if it works for your scenario? If it doesn't, we can check this PR again.

Thank you!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale