[GH-ISSUE #1727] Document HelmForge chart as a third-party Kubernetes installation option #1201

New issue

Open

opened 2026-05-07 01:00:48 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 01:00:48 +02:00

Owner

Originally created by @mberlofa on GitHub (May 6, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1727

Hi ntfy team,

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

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

Example installation:

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

OCI installation:

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

The chart uses the official binwiederhier/ntfy image and supports common Kubernetes deployment needs, including persistent storage for cache/auth data, Service, Ingress, Gateway API HTTPRoute, dual-stack Service fields, Prometheus metrics with optional ServiceMonitor, probes, resource/security settings, scheduling options, and extra manifests. The chart also documents the single-instance limitation because ntfy's default SQLite storage should not be treated as a horizontally scalable multi-writer database.

Would you be open to adding this to the ntfy 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 ntfy project.

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

Originally created by @mberlofa on GitHub (May 6, 2026). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1727 Hi ntfy team, I maintain charts in the HelmForge ecosystem and wanted to share that ntfy is available as a third-party Helm chart for Kubernetes users: - Chart documentation: https://helmforge.dev/docs/charts/ntfy - Chart source: https://github.com/helmforgedev/charts/tree/main/charts/ntfy - Helm repository: https://repo.helmforge.dev - OCI package: `oci://ghcr.io/helmforgedev/helm/ntfy` Example installation: ```bash helm repo add helmforge https://repo.helmforge.dev helm repo update helm install ntfy helmforge/ntfy ``` OCI installation: ```bash helm install ntfy oci://ghcr.io/helmforgedev/helm/ntfy ``` The chart uses the official `binwiederhier/ntfy` image and supports common Kubernetes deployment needs, including persistent storage for cache/auth data, Service, Ingress, Gateway API HTTPRoute, dual-stack Service fields, Prometheus metrics with optional ServiceMonitor, probes, resource/security settings, scheduling options, and extra manifests. The chart also documents the single-instance limitation because ntfy's default SQLite storage should not be treated as a horizontally scalable multi-writer database. Would you be open to adding this to the ntfy 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 ntfy project. If preferred, I can open a small documentation PR with a short third-party Kubernetes/Helm section linking to the HelmForge chart.