Replies: 2 comments
|
Good news — this already works today. The path is just different from what you guessed: it's Installinghelm install coder oci://ghcr.io/coder/chart/coder \
--namespace coder \
--values values.yaml \
--version 2.35.3
Available charts
Note There's no DocsThis is covered at https://coder.com/docs/install/kubernetes, but the OCI reference sits right next to the |
|
sorry, I missed it. Thanks for your explanation! |
Uh oh!
There was an error while loading. Please reload this page.
Description
Currently, the Coder Helm charts are only available via the traditional Helm repository (https://coder.com).
Distributing Helm charts as OCI artifacts via a container registry (like GitHub Packages
ghcr.ioor Docker Hub) has become a cloud-native standard. It improves security, reliability, and allows smoother integration into modern GitOps pipelines (e.g., FluxCD or ArgoCD), which natively support OCI registries.Use Case
We want to manage and mirror our infrastructure dependencies solely through OCI registries. Pulling traditional Helm repositories requires separate configurations and tools compared to standard container images. Having an official OCI registry source would simplify our deployment workflows.
Proposed Solution
Publish the official
coderHelm chart to an OCI-compliant registry alongside the traditional repository.Ideally, this could be hosted on GitHub Packages:
Alternatives Considered
We can manually download (
helm pull), repackage, and push the chart to our private OCI registry (helm push). However, this introduces an extra maintenance burden on our side for every new Coder release.Additional Context
Many modern open-source projects (e.g., Bitnami, Argo, Cert-Manager) already dual-publish or fully migrated their charts to OCI artifacts due to better caching and unified authentication.
All reactions