registry.k8s.io

README

registry.k8s.io

This project implements the backend for registry.k8s.io, Kubernetes's container image registry.

For more details on the implementation see cmd/archeio

The community deployment configs are documented at in the k8s.io repo with the rest of the community infra deployments: https://github.com/kubernetes/k8s.io/tree/main/registry.k8s.io

For publishing to registry.k8s.io, refer to the docs at https://git.k8s.io/k8s.io/k8s.gcr.io#managing-kubernetes-container-registries

Stability

registry.k8s.io is GA and we ask that all users migrate from k8s.gcr.io as soon as possible.

However, unequivocally: DO NOT depend on the implementation details of this registry.

Other than registry.k8s.io serving a compliant OCI registry, API endpoints and backing services used are subject to change at anytime as needed by the project and as resources become available to us.

If you need to allow-list domains to pull these images, we highly recommend mirroring them instead.

The Kubernetes project is currently sending traffic to GCP and AWS thanks to their donations but we hope to redirect traffic to more sponsors and their respective API endpoints in the future to keep the project sustainable.

Please note that there is also No SLA as this is a free, volunteer managed service. We will however do our best to respond to issues and the system is designed to be low-touch.

Privacy

This project abides by the Linux Foundation privacy policy, as documented at https://registry.k8s.io/privacy

Background

Previously all of Kubernetes' image hosting has been out of gcr.io ("Google Container Registry").

We've incurred significant egress traffic costs from users on other cloud providers in particular in doing so, severely limiting our ability to use the infra budget for purposes other than hosting end-user downloads.

We're now moving to shift all traffic behind a community controlled domain, so we can quickly implement cost-cutting measures like serving the bulk of the traffic for AWS-users from AWS-local storage funded by Amazon, or potentially leveraging other providers in the future.

For additional context on why we did this and what we're changing about kubernetes images see https://github.com/kubernetes/k8s.io/wiki/New-Registry-url-for-Kubernetes-(registry.k8s.io)

Essentially, this repo implements the backend sources for the steps outlined there.

Community, discussion, contribution, and support

Learn how to engage with the Kubernetes community on the community page.

You can reach the maintainers of this project at:

• Slack in channel #sig-k8s-infra
• Mailing List

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.