QuestionQ118

VerifiedBuilding and implementing CI/CD pipelines, including continuous testing, for application, infrastructure, and machine learning workloads

You are designing a CI/CD pipeline that deploys a containerized application from your GitHub repository to Artifact Registry. The build process must trigger whenever a new tag is created. The build requires approval from the [email protected] Google group. To satisfy your company’s security requirements, you must avoid static credentials and federation with any other system.

How should you configure the CI/CD pipeline?

Explanation

A Cloud Build GitHub trigger can be configured for a Push new tag event and to require approval before its build executes. The roles/cloudbuild.builds.approver role grants the permission to approve or reject pending builds, so it should be assigned to the required Google group. The service account used by the trigger needs roles/artifactregistry.writer to upload the container image to Artifact Registry. This native Cloud Build integration avoids both a static service-account key and external workload identity federation.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!