Image repositories

Container runtimes like docker, podman, or local Kubernetes installations cache the images provided by kgs in a image repository (also called image registry) without any configuration.

Cloud environments like AWS Fargate or Azure Container Apps, Azure Kubernetes Services, Amazon Elastic Kubernetes Service do not cache image by default. Instead whenever a container is started, the image is downloaded again from kgs Nexus. This may cause load and security problems which kgs needs to respond to.

kgs reserves the right to temporarily withdraw or or limit the traffic of images due to load restrictions or security reasons.
kgs does not guarantee the 24/7-availability of the Nexus image repository.

kgs strongly recommends to use an image repository to keep copies of downloaded images. Using an image repository improves image availability, deployment efficiency, and container startup time.

There are many offerings available for image repositorys. kgs does not favour one over the other. So the list below is neither a complete overview, nor a list of recommendations.

Runtime	Registry or cache

Runtime	Registry or cache
docker	local cache for single instances inbuild, registry can be configured
podman	local cache for single instances inbuild, registry can be configured
Kubernetes	local cache (per node) available, but registry recommended
Azure Kubernetes Service	https://azure.microsoft.com/de-de/products/container-registry
Amazon Elastic Kubernetes Service	https://aws.amazon.com/ecr/
other Service	look for specific caches or use generic registries