IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

Removed Helm reference

Browse Source 
Signed-off-by: AbstractionFactory <179820029+abstractionfactory@users.noreply.github.com>
Co-authored-by: Martin Atkins <mart@degeneration.co.uk>
This commit is contained in:
AbstractionFactory 2025-02-03 19:05:07 +01:00 committed by Martin Atkins
parent b0b38de220
commit 1d2da46f25
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
rfc/20241206-oci-registries.md
View File

@ -6,7 +6,7 @@ Issue: https://github.com/opentofu/opentofu/issues/308
OCI registries (also historically known as Docker registries) form the backbone of the container ecosystem. They present an easy way to publish self-contained miniature operating system userland images that users can run without installing additional libraries or tools beyond a container engine. The main feature of an OCI registry is its ability to publish layers containing differential changes, making container image updates very efficient.
However, thanks to the generic architecture of OCI registries, several implementations have popped up that allow users to store arbitrary data in OCI registries beyond container images. For example, [OCI Registry As Storage (ORAS)](https://oras.land/) is such a project, but the [Helm project also supports OCI storage](https://helm.sh/docs/topics/registries/).
However, thanks to the generic architecture of OCI registries, several implementations have popped up that allow users to store arbitrary data in OCI registries beyond container images. For example, [OCI Registry As Storage (ORAS)](https://oras.land/) is such a project.
The OCI registry standardization and the implementation of the OpenTofu/Terraform Registry protocols (the latter used by OpenTofu) happened around the same time (see [here for providers](https://opentofu.org/docs/internals/provider-registry-protocol/) and [here for modules](https://opentofu.org/docs/internals/module-registry-protocol/)). These protocols followed different design goals. For example, the provider registry protocol concerns itself with artifact signing and decoupling the index and the download part of the registry, whereas OCI is concerned, for example, with layer pull efficiency. To this day OCI image signing is still in development and only a partially solved problem, with projects like [sigstore/cosign](https://www.sigstore.dev/) attempting to take a stab the issue.