Closed mattcary closed 4 months ago
/sig testing
Currently the test uses the default service account for GCE instead of a specific service account.
I0212 20:46:57.674362 7020 setup_e2e_test.go:94] Running in project k8s-infra-e2e-boskos-067 with service account 392769659984-compute@developer.gserviceaccount.com
The SA prow-build@
has the correct role https://github.com/kubernetes/k8s.io/pull/6414
@mattcary Can you make sure all the tests use the SA prow-build@
?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
This is working now :-)
31863 moved the pd csi driver to some new cluster and set of projects, however it was apparently never verified that those projects actually work to run the test.
The cluster service account is missing roles/cloudkms.cryptoKeyEncrypterDecrypter.
I think a change needs to be made to k8s.io/k8s.io/infra/gcp somewhere, but with the partial migration from bash to terraform I'm not sure what to change.
For now I'll revert the change that broke our e2e test; any suggestions on how to correctly set up the cluster service account in the terraform world are welcome!