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 Workload Identity Authentication #718

Open
papaymaguire opened this issue Nov 8, 2024 · 0 comments
Open

GKE Workload Identity Authentication #718

papaymaguire opened this issue Nov 8, 2024 · 0 comments

Comments

@papaymaguire
Copy link

Hello,

I am using Google Kubernetes Engine to deploy my application and s3proxy. Workload Identity ties together a Google Service Account and a Kubernetes Service Account allowing pods running under that service account to make authenticated calls to the Google APIs. I want to use this to authenticate s3proxy rather than using explicit identity and credential fields.

I am trying to figure out exactly how this works and how I can integrate it with s3proxy. I am not quite sure if Workload Identity just places a credential on the pod when it spins up and I could feed that to JClouds or it may intercept requests and authenticate them automatically, in which case I would just have to get JClouds to try and make the requests without supplying credentials. Any thoughts? Has anyone tried this before?

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

No branches or pull requests

1 participant