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.

Sign up for GitHub

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

Jump to bottom

Use workload identity for gcp-guest #223

Open
6 tasks
fejta opened this issue Jan 10, 2020 · 2 comments
Open
6 tasks

Use workload identity for gcp-guest #223

fejta opened this issue Jan 10, 2020 · 2 comments
Assignees
@hopkiw

Comments

@fejta
Copy link
Contributor

fejta commented Jan 10, 2020 •
edited
Loading

/assign @hopkiw
#202

Instructions:

  • Run enable-workload-identity.sh on the build cluster
    • cluster: gcp-guest
  • Run bind-service-accounts.sh for the service account pair
    • secretName: daisy-service-account
  • Ensure job does not depend on the secret.json file existing
  • Update job to use a serviceAccountName, stop using the secret
@fejta
Copy link
Contributor Author

fejta commented Jan 10, 2020

Actually since these jobs run on your own cluster, feel free to manage this however you want, but workload identity is the best practice for authenticating to GCP inside a GKE pod

https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity

@fejta fejta mentioned this issue Jan 10, 2020
Open
7 tasks
@fejta
Copy link
Contributor Author

fejta commented Jan 15, 2021

Also potentially helpful: https://github.com/kubernetes/test-infra/tree/master/workload-identity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hopkiw hopkiw

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fejta @hopkiw