Document HelmForge chart as a third-party Kubernetes installation option

[mberlofa]

Hi Umami team,

I maintain charts in the HelmForge ecosystem and wanted to share that Umami is available as a third-party Helm chart for Kubernetes users:

• Chart documentation: https://helmforge.dev/docs/charts/umami
• Chart source: https://github.com/helmforgedev/charts/tree/main/charts/umami
• Helm repository: https://repo.helmforge.dev
• OCI package: oci://ghcr.io/helmforgedev/helm/umami

Example installation:

helm repo add helmforge https://repo.helmforge.dev
helm repo update
helm install umami helmforge/umami

OCI installation:

helm install umami oci://ghcr.io/helmforgedev/helm/umami

The chart uses the official ghcr.io/umami-software/umami image and supports common Kubernetes deployment needs, including a bundled HelmForge PostgreSQL subchart or external PostgreSQL database, generated or existing app secrets, Ingress, Gateway API HTTPRoute, External Secrets Operator integration, dual-stack Service fields, PostgreSQL backup support, probes, resource/security settings, scheduling options, and extra manifests.

Would you be open to adding this to the Umami documentation as an unofficial / third-party Kubernetes installation method? This could help users who already run self-hosted apps on Kubernetes discover a maintained Helm-based deployment path, while keeping ownership clear that the chart is maintained by HelmForge and not by the upstream Umami project.

If preferred, I can open a small documentation PR with a short third-party Kubernetes/Helm section linking to the HelmForge chart.

[mikecao]

Sure, just submit a PR to our docs repo, https://github.com/umami-software/docs

[mberlofa]

Hi @mikecao, thanks for the direction.

I opened a PR in the docs repo adding HelmForge as a third-party Kubernetes installation option on the Installation page:

umami-software/docs#23

The PR covers Helm install commands, bundled PostgreSQL, external PostgreSQL, port-forward access, Ingress, and links to the HelmForge chart documentation/source.

I validated it locally with pnpm install --frozen-lockfile and pnpm build. The remote Vercel checks currently require authorization from a member of the Umami Software Vercel team because the PR comes from a fork.