longhorn/charts

Helm Charts

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

longhorn/charts has 90+ stars and 80+ forks on GitHub, is written in Mustache, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 26 minutes ago
Type:Template / ExampleCategory(s):Kubernetes & OperatorsCloud Native & Infrastructure
Added to GitGenius on October 15th, 2026
Created on July 6th, 2020
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 83
Total Stargazers: 98 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Longhorn Charts is a Helm chart repository that packages Longhorn for Kubernetes deployment.

The repository solves the problem of installing Longhorn, a distributed block storage system for Kubernetes, by providing a standardized Helm chart. The approach is straightforward: charts are copied from the source Longhorn repository into the charts directory when ready for release, then automated workflows package and publish them to GitHub Pages.

Teams adopting this should understand that it serves as the official distribution mechanism for Longhorn via Helm. It suits any Kubernetes cluster needing persistent block storage through Longhorn. The repository is designed as a release artifact store rather than a development environment; the README explicitly notes that changes should only be synced when ready for release, and that direct modifications to charts in this repository will cause GitHub Actions to fail, since Chart Releaser will not override existing releases.

The project maintains a structured release process where GitHub Actions automatically detects changes to charts since the last tagged release, packages them, and publishes to GitHub Pages. The workflow is gated to prevent accidental direct edits that would conflict with the release mechanism.