Helm charts for deploying MetricsHub on Kubernetes.
helm repo add metricshub https://metricshub.github.io/helm-charts
helm repo update
helm search repo metricshubCharts are also published as OCI artifacts, no helm repo add needed:
helm show values oci://ghcr.io/metricshub/charts/m8b-stack| Chart | Latest release | Description |
|---|---|---|
| m8b-stack |  |
AI assistant in Slack that answers questions about your infrastructure from live MetricsHub data, metrics history and documentation, with your own LLM. Deploys MetricsHub Enterprise, Prometheus, SearXNG and the M8B bot. |
New to Helm? Start with the m8b-stack getting-started guide. Each chart's README documents prerequisites, required Secrets and values. Charts never embed credentials: they reference Kubernetes Secrets you create.
charts/<name>/ one directory per chart (Chart.yaml, values.yaml, values.schema.json, templates/, examples/)
tests/<name>/ unit tests for scripts shipped inside a chart
scripts/test.sh offline checks run by CI: helm lint, render matrix, rejected values, unit tests
pom.xml, src/site/ documentation site (https://metricshub.org/helm-charts), built from the Markdown files
./scripts/test.sh # requires helm and node
mvn site # requires JDK 25; documentation preview in target/site/index.htmlEach chart is versioned independently in its Chart.yaml; the repository itself has no version. The badges read
the published index.yaml, so they always show the latest released version.
Bump version in Chart.yaml for every chart change; CI enforces it on pull requests.
Releases are manual: in GitHub, Actions > Release > Run workflow on main. The workflow runs the tests, then
publishes every chart whose version has no release yet to GitHub Releases, the Helm index and GHCR, and redeploys the
documentation site.
Pushing to main alone never publishes anything.
The charts in this repository are released under the MIT License. The container images they deploy (MetricsHub Enterprise, M8B) are distributed under their own terms and require registry credentials.