pull-secrets-store-csi-driver-e2e-gcp job failing

[aramase]

This PR job has been failing for PRs

Some of the PRs:
#412
#413
#417

/kind failing-test
cc @tam7t

[aramase]

/assign @tam7t

[tam7t]

The gcp-secrets-store-cred from https://github.com/kubernetes/test-infra/blob/c50d055243429b918a2539b4ad86f91dce550520/config/jobs/kubernetes-sigs/secrets-store-csi-driver/secrets-store-csi-driver-presets.yaml#L36 has expired.

I've generated a new one and waiting for test infra to be updated.

[tam7t]

the new one will expire on 5 April, so I'll need to rotate before then again 😢

[aramase]

Looks like the new creds are ready for use: https://kubernetes.slack.com/archives/C09QZ4DQB/p1609881564374600

Trying on a PR to confirm it's working.

[aramase]

Creds are fixed now. The tests are green again.

@tam7t I think we should have an issue to remind rotating the creds again on 5th April. We can open an issue here or the gcp provider. WDYT?

[tam7t]

As discussed in the sig meeting today I'll reach out to #sig-testing to see if there's another auth mechanism that doesn't require manual rotation.

[aramase]

@tam7t What was the outcome of the discussion with #sig-testing? Should we close this issue now?

[tam7t]

/close

We want a separate credential to isolate workloads. This will be on me/Google team to setup alerts to manually rotate for the time being.

[k8s-ci-robot]

@tam7t: Closing this issue.

In response to this:

/close

We want a separate credential to isolate workloads. This will be on me/Google team to setup alerts to manually rotate for the time being.

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.