K8s-Borg
A Helm chart that backs up Kubernetes clusters with BorgBackup by deploying node, cluster-data, and console workloads to separate Borg repositories.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
55/100 Fair
- Maintained
- 100last commit 5 days ago
- Popular
- 61 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 1
- Open issues
- 2
- Last commit
- 2026-11-16
- Latest release
- 1.3.6
- License
- AGPL-3.0
- Activity
- steady
Checked 5 days ago - source: GitHub (ioanalytica/k8s-borg)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Add the NATS repo and install NATS Add the NATS Helm repository, then install the NATS chart with a release name like my-nats. If you skip the repository step, Helm cannot find the NATS package and the install will fail. source
- Turn on login before first start Enable client authentication and set a username and password, either in the command or a values file, before installing. Without these settings, NATS may be reachable by anyone who finds the port. source
- Point NACK at the right NATS URL If you install NACK, enable JetStream and clustering in NATS and give NACK the NATS URL nats://nats.default.svc.cluster.local:4222. If that address is wrong or JetStream is disabled, NACK cannot store its managed topic settings. source
- Install the Helm chart Create a k8s-borg namespace and install the release with helm install, specifying the chart version and your values.yaml file. source
Fetched 5 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I specify which paths k8s-borg should back up?
The chart names no paths by default. You provide them as R roots, for example by adding /node/etc to a node.include value.
Can k8s-borg run both the Borg UI and a Borg repository server in one release?
Yes. The chart can optionally deploy a Borg UI server with managed agents, and a repository server for Borg 1 or Borg 2 can run in the same release.
How should I pass the repository passphrase and SSH key in a real cluster?
For anything beyond a smoke test, put the sensitive values in a pre-created Secret and reference that Secret with existingSecret.
Is there a way to test k8s-borg without a dedicated Borg machine?
The try-locally guide runs the whole chart in a throwaway k3d cluster, with Borg UI and managed agents, up to a first backup and restore.
Answers sourced from github.com
Community
- [OFFICIAL] k8s-borg · Issue #4937 · artifacthub/hub · GitHub (forum)
- When comparing Borg vs. K8s: \* Borg is primarily for managing hardware ... (other)
Collected 5 days ago - public community threads