GKE Default Credentials and Temporary Access Tokens #63
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.
Signed-off-by: Brad Wadsworth brad.wadsworth@mavenwave.com
Description of your changes
This change will allow InjectedIdentity via GKE workload identity to be used in order to authenticate to a GKE cluster. Moreover, in addition to service account keys being used as secrets, temporary access tokens may also be used. The access tokens may be created from a CronJob that regenerates the token every hour.
Fixes #36
I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Tested in a GKE cluster in order to verify workload identity.