Comparison
Artefact registryvsContainer registry
Artefact registry
every build output is stored somewhere with a version and a retention policy, and deploying is a pull from there.
The store that holds published build outputs, with versioning, access control, retention and often scanning attached. It is the seam between build and deploy, and it is a production dependency: if it is unavailable, nothing scales up and no node is replaced. Retention policy is where it bites — the rollback target you need is the one the cleanup job deleted last week.
Full entry →Container registry
the deploy failed at three in the morning because the place you pull images from was rate-limiting you, and it is not your infrastructure.
The service that stores and serves images, addressed by repository, tag and digest. It is a hard dependency of every scale-up and every node replacement, which makes a public registry a single point of failure that your architecture diagram does not show. Teams reach for a pull-through cache or an internal mirror the first time a rate limit or an outage takes production capacity with it.
Full entry →