You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Helm v3.8.0, the OCI support became GA, which is an excellent chance to start publishing Helm charts to OCI-compliant registries.
Use cases
OCI registries are widely adopted and are fast becoming the standard. Now that Helm supports these by default it would be nice if 1p could push their charts to an OCI registry, e.g. ghcr.io.
Using the OCI standard also allows for the charts to be signed with cosign. This will provide a way for end users to check the integrity of the charts.
Proposed solution
Publish charts to an OCI registry like ghcr.io.
The text was updated successfully, but these errors were encountered:
>[!IMPORTANT]
> After this is merged and charts are released you might need to make the packages public from [here](https://github.com/orgs/1Password/packages)
I also bumped some deps as well and switched back to the official chart releaser action.
Fixes: 1Password#221
Summary
With Helm v3.8.0, the OCI support became GA, which is an excellent chance to start publishing Helm charts to OCI-compliant registries.
Use cases
OCI registries are widely adopted and are fast becoming the standard. Now that Helm supports these by default it would be nice if 1p could push their charts to an OCI registry, e.g. ghcr.io.
Using the OCI standard also allows for the charts to be signed with cosign. This will provide a way for end users to check the integrity of the charts.
Proposed solution
Publish charts to an OCI registry like ghcr.io.
The text was updated successfully, but these errors were encountered: