Closed nesmabadr closed 2 weeks ago
Only pipelines/jobs/actions/... controlled by the Neighbors are allowed to upload images to our registry, especially the productive one. We can think about providing some kind of dev registry to cache images for testing purposes (if this makes sense?). The images from this dev registry must not reach the productive registry!
Description
As a part of the prow jobs migration from the Neighbors's Prow, we wanted to migrate the release-template-operator-assets to a Github Action in the Template Operator repo. But for this we need to get access to the kyma-project since we are using the Github action, so we need to have a service account name, a workload identity provider and to give our repo some access to the GCP project.
specifically: Assign
principalset://iam.googleapis.com/projects/718973091829/locations/global/workloadIdentityPools/github-action/attribute.repository/kyma-project/template-operator
asService Account Token Creator
as well asWorkload Identity User
Reasons
To allow the job to work correctly with GitHub Actions
Acceptance Criteria
This is blocking https://github.com/kyma-project/test-infra/issues/9495 Attachments