Use workload identity for esp-v2

[fejta]

/assign @hopkiw

ref #202

• Run enable-workload-identity.sh on the build cluster
• Run bind-service-accounts.sh for the service account pair
  • secretName: service-account
  • secretName: cloudesf-testing-github-prow-service-account
• Ensure job does not depend on the secret.json file existing, or the GOOGLE_APPLICATION_CREDENTIALS environment variable being set
• Update job to use a serviceAccountName, stop using the secret (example: Use workload-identity to deploy prow #221)

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

[fejta]

Since these jobs run on the shared prow.gflocks.com build cluster, rather than your own cluster, these need to get migrated as we plan to soon delete the above two secrets (especially the shared service-account secret)

[fejta]

/assign @TAOXUY

[google-oss-robot]

@fejta: GitHub didn't allow me to assign the following users: TAOXUY.

Note that only GoogleCloudPlatform members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @TAOXUY

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fejta]

Thanks Xuyang!
/close

[google-oss-robot]

@fejta: Closing this issue.

In response to this:

Thanks Xuyang!
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.