A container registry stores container image data and makes images available for Kubernetes to fetch. It connects the local image you build on your machine with the cloud environment where Kubernetes runs it. section 3.2.2
Registries can be public or private. Public images suit open-source projects, shared samples, and common base images; private images protect proprietary applications and require authentication. section 3.2.2
A practical upload workflow is:
- Create an account and a repository with the registry provider. section 3.2.2
- Configure authentication, especially when using private images. section 3.2.2
- Tag the local image with the registry host, project or username, repository, and version tag. section 3.2.2
- Push the tagged image so Kubernetes can retrieve it during deployment. section 3.2.2 section 3.5
Uploading a versioned image
A local image named timeserver can be tagged as us-docker.pkg.dev/wdenniss/ts/timeserver:1 and pushed to Artifact Registry. Kubernetes can then use that repository path and version tag when creating the workload. section 3.2.2 section 3.5
Docker Hub is a common public choice. For private images, a cloud provider’s registry commonly simplifies authentication and can reduce image-pull time and network data costs. section 3.2.2
