Registry in Yandex Cloud Registry

A registry is a centralized repository as well as a management tool for the various files used in app development and deployment.

Each registry may contain a set of package versions associated with particular resources. Use Maven CLI, NPM, or NuGet CLI to retrieve and publish packages.

With a registry, you can quickly access the artifacts you need and manage their versions. Using a registry simplifies the process of managing dependencies between the project components. This feature will be of use to development teams working on large and complex projects.

Registries share the same data centers with your infrastructure for speedy performance without needless traffic costs.

Registry types in Cloud RegistryRegistry types in Cloud Registry

Depending on artifact storage location, Cloud Registry registries can be local, remote, or virtual.

Local registriesLocal registries

Local registries allow you to store, securely distribute, and manage artifacts (Docker images, Helm charts, binary files, etc.) created within your organization. Local registries are centralized and secure storage facilities for internal binary data.

Remote registriesRemote registries

Remote registries operate as proxies for remote repositories, such as Docker Hub or other third-party repositories. Remote registries enable local caching of artifacts after initial access, thus accelerating access to frequently used data and reducing load on source remote resources.

With Cloud Registry, developers can upload code libraries, software packages, and other development artifacts into remote registries for storage.

Custom registriesCustom registries

Custom registries are a type of remote registries where the user specifies the source of artifacts manually instead of using a default public source. A custom source address must:

• Point to a specific registry rather than a shared host, because different cloud providers and artifact management systems may serve multiple registries under a single domain.
• Begin with http:// or https://.

Example of correct Docker registry addresses:

https://registry.yandexcloud.net/v2/registry-id
https://registry-1.docker.io/v2/registry-id

Virtual registriesVirtual registries

Multiple local and/or remote registries can be combined under a single name with the help of virtual registries, providing a single entry point to search and download required artifacts. Virtual registries simplify access and management because, with the single entry point, users do not have to think about the physical location of registries.