Harish's Helm Charts

Reliable Helm charts for self-hosted Kubernetes applications. This repository provides practical, versioned charts for media automation, analytics, dashboards, networking, monitoring, finance, storage, security, and homelab services.

Every chart is published through both the classic Helm repository format and as an OCI chart in GHCR, so users can install through the workflow they already prefer.

Browse the chart catalog to search applications, filter by category, and copy versioned Helm or OCI installation commands. Charts are created and maintained by Harish.

Highlights

• Dual publishing: GitHub Pages index.yaml and GHCR OCI charts.
• Signed packages: chart archives are published with Helm provenance files.
• Portable defaults: no personal domains, namespaces, storage classes, or cluster-specific controllers assumed.
• Versioned releases: chart packages are attached to GitHub Releases and available from the public repository index.
• Homelab friendly: charts are small, readable, and easy to customize with values files.

Distribution

Channel	Location	Best for
Helm repository	https://charts.harish2k01.in	Classic Helm workflows with helm repo add, helm search repo, and index.yaml.
OCI registry	oci://ghcr.io/harish2k01/helm-charts/<chart-name>	Direct registry installs without adding a Helm repository first.
GitHub Releases	Per-chart version tags	Release notes and downloadable .tgz chart assets.

Quick Start

Install from the Helm repository:

helm repo add harish2k01 https://charts.harish2k01.in
helm repo update
helm install bentopdf harish2k01/bentopdf --version 0.1.3

Install the same chart from GHCR OCI:

helm install bentopdf oci://ghcr.io/harish2k01/helm-charts/bentopdf --version 0.1.3

Customize with your own values:

helm install bentopdf harish2k01/bentopdf -f values.yaml

Browse every published version:

helm search repo harish2k01 --versions

Requirements

• Helm 3
• Access to a Kubernetes cluster
• A configured kubectl context for the target cluster
• Optional: an Ingress controller or Gateway API implementation for external HTTP access

Chart Catalog

The catalog is intentionally focused on deployable self-hosted services. Each chart keeps cluster assumptions out of defaults so it can be reused across different Kubernetes environments.

Chart	Chart Version	App Version	Category	Description
adguard-home	0.2.0	v0.107.79	Network	Deploys AdGuard Home DNS filtering with persistent configuration and DNS service ports.
bazarr	0.3.0	1.6.2	Media	Deploys Bazarr subtitle automation on Kubernetes.
bentopdf	0.3.0	2.8.10	Documents	Deploys BentoPDF document conversion on Kubernetes.
cloudflared	0.2.0	2026.10.2	Network	Deploys Cloudflare Tunnel cloudflared connectors on Kubernetes.
feishin	0.2.0	1.17.0	Media	Deploys Feishin music streaming client on Kubernetes.
firefly-iii	0.2.0	version-6.6.6	Finance	Deploys Firefly III with PostgreSQL for personal finance tracking.

Media Automation Pattern

Media charts are designed to be installed independently. Install the same chart more than once by using different release names and values files:

helm install radarr harish2k01/radarr
helm install radarr4k harish2k01/radarr -f radarr4k-values.yaml
helm install sonarr-anime harish2k01/sonarr -f sonarr-anime-values.yaml

For qBittorrent and the media automation apps, mount the same existing PVC at the same path to preserve hardlinks and atomic moves:

media:
  enabled: true
  existingClaim: media-vault-pvc
  mountPath: /vault
  readOnly: false

Jellyfin can mount selected folders from the same PVC as read-only libraries:

media:
  enabled: true
  existingClaim: media-vault-pvc
  readOnly: true
  mounts:
    - mountPath: /movies
      subPath: Movies
    - mountPath: /tv
      subPath: Shows

Common Commands

Install into a namespace:

helm install bentopdf harish2k01/bentopdf --namespace apps --create-namespace

Upgrade a release:

helm repo update
helm upgrade bentopdf harish2k01/bentopdf -f values.yaml

Upgrade from OCI:

helm upgrade bentopdf oci://ghcr.io/harish2k01/helm-charts/bentopdf --version 0.1.3 -f values.yaml

Uninstall a release:

helm uninstall bentopdf

Repository URLs

Helm repository: https://charts.harish2k01.in
Index file:      https://charts.harish2k01.in/index.yaml
OCI registry:   oci://ghcr.io/harish2k01/helm-charts/<chart-name>

Chart Signing

Release builds sign every chart package with Helm provenance. The public key is published at:

https://charts.harish2k01.in/chart-signing-key.asc

To verify a downloaded package:

curl -fsSLO https://charts.harish2k01.in/chart-signing-key.asc
curl -fsSLO https://charts.harish2k01.in/bentopdf-0.1.3.tgz
curl -fsSLO https://charts.harish2k01.in/bentopdf-0.1.3.tgz.prov
gpg --dearmor < chart-signing-key.asc > chart-signing-key.gpg
helm verify bentopdf-0.1.3.tgz --keyring ./chart-signing-key.gpg

Release Publishing

Published chart versions are immutable. Changes anywhere inside a chart directory, including its README and schema, require a chart version bump. CI checks this on pull requests and pushes to main.

The release workflow reuses existing signed archives, packages new versions, and repairs incomplete GitHub release assets. Historical packages remain available through the Helm index. History downloads run four at a time, and any failed restoration stops deployment.

Successful OCI checks and publications are recorded by archive SHA-256 in the site's release-state.json. Later releases skip confirmed versions; a missing state file triggers a full check. The state is deployed only after OCI publishing and GitHub release creation succeed. Chart source fingerprints also prevent an existing version from being reused after its source changes.

To repair OCI versions removed outside the workflow, run Release Charts manually with reconcile enabled. This checks all historical versions even when publication receipts exist. The first optimized release performs that same full OCI check to establish the initial state.

Catalog Website

The catalog is a static website served by GitHub Pages at https://charts.harish2k01.in. It includes app logos from chart metadata, light and dark themes, search/category filters, and installation details for every chart in one scrolling list. The H/home/server mark identifies Harish's homelab and serves as the favicon.

Application logos come from the selfh.st icon collection where available, using the icon URL in each chart's metadata. Charts without a suitable logo display app initials.

docs/catalog.json is generated from chart metadata in charts/*/Chart.yaml and categories in the chart table above. To refresh it locally with Node.js 24:

npm ci --ignore-scripts
npm run build:catalog
npm run check:catalog
npm run test:catalog

Serve docs/ with a local HTTP server to preview the site; the catalog loads its JSON over HTTP. CI checks that the committed catalog matches the charts, and the release workflow regenerates it before publishing the Pages artifact. The website itself needs no Node.js server or frontend framework.