From 6c044a76f3191426513748af4f95d7d8071581bc Mon Sep 17 00:00:00 2001 From: Aaron Crickenberger Date: Thu, 14 Jan 2021 21:44:27 -0500 Subject: [PATCH] Enable GCR for e2e projects This is needed specifically by the scale projects to be able to run kubemark, but I would like the "push to GCR repo in the project boskos gave to my job, with no expectation the image will live beyond the job" pattern to be possible for all e2e projects. --- infra/gcp/ensure-e2e-projects.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/infra/gcp/ensure-e2e-projects.sh b/infra/gcp/ensure-e2e-projects.sh index 93316e7e81c..69c8c0988c0 100755 --- a/infra/gcp/ensure-e2e-projects.sh +++ b/infra/gcp/ensure-e2e-projects.sh @@ -122,6 +122,7 @@ for prj; do enable_api "${prj}" logging.googleapis.com enable_api "${prj}" monitoring.googleapis.com enable_api "${prj}" storage-component.googleapis.com + enable_api "${prj}" containerregistry.googleapis.com color 6 "Empower prow-build service account to edit e2e project: ${prj}" # TODO: this is what prow.k8s.io uses today, but it is likely over-permissioned, we could