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

GKE Default Credentials and Temporary Access Tokens #63

Conversation

bradkwadsworth-mw
Copy link

Signed-off-by: Brad Wadsworth [email protected]

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:

  • Read and followed Crossplane's [contribution process].
  • Run 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.

Brad Wadsworth added 2 commits October 12, 2022 16:00
Signed-off-by: Brad Wadsworth <[email protected]>
Signed-off-by: Brad Wadsworth <[email protected]>
@turkenh
Copy link
Collaborator

turkenh commented Aug 18, 2023

@bradkwadsworth-mw thanks a lot for your contributions 🙌
Looks like this is equivalent to crossplane-contrib/provider-helm#136. Could you update this PR with the latest state after reviews there?

@turkenh turkenh changed the title Added alternative auth methods GKE Default Credentials and Temporary Access Tokens Aug 18, 2023
@turkenh
Copy link
Collaborator

turkenh commented Feb 8, 2024

Closing in favor of #180

@turkenh turkenh closed this Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use GKE Workload Identity for ProviderConfig Identity
2 participants