https://github.com/nebari-dev/helm-repository
Automated Helm chart repository for the Nebari ecosystem — published via GitHub Pages and quay.io OCI registry
https://github.com/nebari-dev/helm-repository
Last synced: 17 days ago
JSON representation
Automated Helm chart repository for the Nebari ecosystem — published via GitHub Pages and quay.io OCI registry
- Host: GitHub
- URL: https://github.com/nebari-dev/helm-repository
- Owner: nebari-dev
- License: apache-2.0
- Created: 2026-03-05T11:37:18.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2026-06-12T09:50:05.000Z (17 days ago)
- Last Synced: 2026-06-12T11:14:09.456Z (17 days ago)
- Language: Go Template
- Homepage: https://nebari-dev.github.io/helm-repository/
- Size: 2.1 MB
- Stars: 2
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Nebari Helm Repository
[](https://github.com/nebari-dev/helm-repository/actions/workflows/release-helm-charts.yml)
[](LICENSE)
[](https://nebari-dev.github.io/helm-repository/)
An automated Helm chart repository for the [Nebari](https://nebari.dev) ecosystem, published via GitHub Pages.
| | |
|---|---|
| **Chart catalog** | https://nebari-dev.github.io/helm-repository/ |
| **Helm index URL** | `https://raw.githubusercontent.com/nebari-dev/helm-repository/gh-pages/` |
| **Raw index.yaml** | https://raw.githubusercontent.com/nebari-dev/helm-repository/gh-pages/index.yaml |
## Using the repository
### Option A — Helm index (classic)
```bash
# Add the repository
helm repo add nebari https://raw.githubusercontent.com/nebari-dev/helm-repository/gh-pages/
# Update the local cache
helm repo update nebari
# List available charts
helm search repo nebari
# Install a chart
helm install my-release nebari/
```
#### Private repository access (GitHub Enterprise)
```bash
helm repo add nebari \
https://raw.githubusercontent.com/nebari-dev/helm-repository/gh-pages/ \
--username \
--password
```
### Option B — OCI registry (quay.io)
Charts are also published as OCI artifacts to `quay.io/nebari/charts`. No `helm repo add` step is required.
```bash
# Install directly — version flag is required for OCI
helm install my-release oci://quay.io/nebari/charts/ --version
# Pull without installing
helm pull oci://quay.io/nebari/charts/ --version
# Inspect chart metadata
helm show chart oci://quay.io/nebari/charts/ --version
```
> OCI charts are public and require no authentication to pull. The OCI reference for each chart is shown in the
> [chart catalog](https://nebari-dev.github.io/helm-repository/).
## Publishing a new chart
Chart **source directories** live in `charts/` on `main`. You never need to run `helm package` manually — CI does it.
1. Scaffold or copy your chart into `charts/`:
```bash
helm create charts/my-chart
# edit Chart.yaml, values.yaml, templates/ …
```
2. Commit and push to `main`:
```bash
git add charts/my-chart
git commit -m "feat: add my-chart v1.0.0"
git push
```
The [Release Helm Charts](.github/workflows/release-helm-charts.yml) GitHub Actions workflow will automatically:
- Run `helm package` on every directory under `charts/`
- Merge the new packages into `index.yaml` on `gh-pages` (preserving historical `created` timestamps)
- Copy chart archives to `helm/` on `gh-pages`
> **`gh-pages` is CI-managed for chart releases.** The landing page (`index.html`) lives directly on `gh-pages` — update
> it there via a PR targeting that branch.
## Syncing charts from other repositories (automated)
Tool repositories can sync their Helm chart into this repo automatically using the
[`sync-chart`](.github/actions/sync-chart/action.yml) composite action. When a new release is published in the tool
repo, the action:
1. Copies the chart source directory into `charts//` here.
2. Opens a PR against `main` for review.
3. On merge, the existing **Release Helm Charts** workflow packages and publishes it.
> This is set up by **helm-repository maintainers** using the Nebari bot account. See the
> [maintainer setup guide](.github/actions/sync-chart/README.md) for token creation, organisation secret configuration,
> and per-repo rollout steps.