Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove prow-build service account from group, grant permissions directly #1401

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion groups/sig-release/groups.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,6 @@ groups:
- [email protected]
- [email protected]
- [email protected]
- [email protected]

- email-id: [email protected]
name: k8s-infra-staging-cip-test
Expand Down
12 changes: 12 additions & 0 deletions infra/gcp/ensure-staging-storage.sh
Original file line number Diff line number Diff line change
Expand Up @@ -274,3 +274,15 @@ for repo in "${WINDOWS_REMOTE_DOCKER_PROJECTS[@]}"; do
done
) 2>&1 | indent
done

# Special case: In order for ci-kubernetes-build to run on k8s-infra-prow-build,
# it needs write access to gcr.io/k8s-staging-ci-images. For now,
# we will grant the prow-build service account write access. Longer
# term we would prefer service accounts per project, and restrictions
# on which jobs can use which service accounts.
color 6 "Configuring special case for k8s-staging-ci-images"
(
PROJECT="k8s-staging-ci-images"
SERVICE_ACCOUNT=$(svc_acct_email "k8s-infra-prow-build" "prow-build")
empower_svcacct_to_write_gcr "${SERVICE_ACCOUNT}" "${PROJECT}"
)