Hands-on Labs

Artifact Registry hygiene for multi-team builds

14 min read · Brief

This brief walks through naming conventions, cleanup automation, and label strategy we teach in week four of the associate engineer path. You will see how we pair Cloud Build triggers with policy checks so nobody ships stale layers to shared environments.

Tuition reference: KRW 1,200,000

What is inside

Separation of dev, staging, and release repositories
Signed attestations before promotion
Budget alerts tied to storage growth, not revenue metrics
Drift detection on IAM bindings for readers
Optional sync to on-prem mirrors for air-gapped labs
Retention windows that match cohort sprint cadence
Hands-on worksheet for rollback drills

Outcomes you can show

You can diagram your own promotion graph
You can explain why immutability tags beat floating latest
You can run the supplied cleanup dry-run safely

Responsible editor

Haneul Park

Technical Lab Engineer focused on build reproducibility and classroom sandboxes.

Participant notes

“The Artifact Registry brief finally made promotion clicks feel intentional. I reused the week-four checklist on our cohort demo.”

Leo · Platform intern · 5/5 · survey

Brief FAQ

No. It is a focused add-on for teams already running containers in class projects.