Add support for pushing Helm charts to OCI registries, rather than just Github Pages-based chart repos. #187
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per #186
This adds support for publishing Helm charts to an OCI registry.
A configuration like
will push the
binderhub
chart to to Github's GHCR OCI registry under the pathghcr.io/jupyterhub/helm-charts/binderhub
This should work for Amazon's OCI repo (ECR), Google's OCI repo (GCR), and Docker's self-hosted
registry
image, all of which are OCI-compliant registries.Additionally, this PR adds support for a
basePath
key under chart definitions, for repos that keep charts under a specific directory structure - this is roughly analogous tocontextPath
for images.This means
chartpress.yaml
can be kept in the repo root, and users have more freedom as to how and where charts and images are kept relative to each other, as well as tochartpress.yaml
itself.