WIP: Added --cache as authorizer option in kubeconf #1412
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I think the credential cache option should be added to the aws-iam-authorizer call as a default, since awscli also uses caching by default. kubernetes-sigs/aws-iam-authenticator#193
This is how the resulting config would look after the PR:
Comments requested: Should I use this as the default or make it configurable? Then I'll complete the PR.
BTW, why doesn't everyone use roles & MFA for doing anything on AWS? Or am I missing something?