secrets-store-csi-driver: gcp use workload identity instead of secret

[tam7t]

Alternative to ExternalSecret syncing, using workload identity for the secrets-store-csi-driver gcp integration tests:

Requires:

• iam: allow k8s prow to act as k8s-csi-test with WI GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp#130
• test: gcp use workload id instead of node publish kubernetes-sigs/secrets-store-csi-driver#641

I've verified that the GCP provider process in the test cases currently runs as the user serviceAccount:k8s-prow-builds.svc.id.goog[test-pods/default]. Switching the pod to a different SA and granting:

serviceAccount:k8s-prow-builds.svc.id.goog[test-pods/secrets-store-csi-driver-gcp] permission to act as k8s-csi-test@secretmanager-csi-build.iam.gserviceaccount.com will allow the test cases to use workload identity instead of exported SA + sync'd secret.

[aramase]

/lgtm

[aramase]

Do you plan on removing

test-infra/config/prow/cluster/build_kubernetes-external-secrets_customresource.yaml

Line 20 in c0c1a41

name: gcp-secrets-store-cred

in a followup PR?

[tam7t]

Do you plan on removing

test-infra/config/prow/cluster/build_kubernetes-external-secrets_customresource.yaml

Line 20 in c0c1a41

name: gcp-secrets-store-cred

in a followup PR?

Yeah, I want to keep that around and remove in a separate PR in case things go wildly wrong

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: e-blackwelder, tam7t

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes-sigs/secrets-store-csi-driver/OWNERS [e-blackwelder,tam7t]
• config/prow/cluster/OWNERS [e-blackwelder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@tam7t: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key secrets-store-csi-driver-config.yaml using file config/jobs/kubernetes-sigs/secrets-store-csi-driver/secrets-store-csi-driver-config.yaml
• key secrets-store-csi-driver-presets.yaml using file config/jobs/kubernetes-sigs/secrets-store-csi-driver/secrets-store-csi-driver-presets.yaml

In response to this:

Alternative to ExternalSecret syncing, using workload identity for the secrets-store-csi-driver gcp integration tests:

Requires:

• iam: allow k8s prow to act as k8s-csi-test with WI GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp#130
• test: gcp use workload id instead of node publish kubernetes-sigs/secrets-store-csi-driver#641

I've verified that the GCP provider process in the test cases currently runs as the user serviceAccount:k8s-prow-builds.svc.id.goog[test-pods/default]. Switching the pod to a different SA and granting:

serviceAccount:k8s-prow-builds.svc.id.goog[test-pods/secrets-store-csi-driver-gcp] permission to act as k8s-csi-test@secretmanager-csi-build.iam.gserviceaccount.com will allow the test cases to use workload identity instead of exported SA + sync'd secret.

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.