Kured

Kured is a Kubernetes DaemonSet that safely reboots nodes when the underlying operating system indicates a reboot is required, helping operators automate node…

  • Infrastructure
  • Tools & Utilities
Kured is a Kubernetes DaemonSet that safely reboots nodes when the underlying operating system indicates a reboot is required, helping operators automate node maintenance while protecting critical workloads.

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.

76/100 Good

Maintained
100last commit 3 days ago
Popular
682,591 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
90no serious findings, CI, tests, OpenSSF Scorecard 7.4/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
2,591
Open issues
61
Last commit
2026-11-18
Latest release
1.23.0
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (kubereboot/kured)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Set the reboot method your system supports Choose whether kured restarts the node with a command such as systemctl reboot or with a system signal. If this is wrong, kured may try to reboot and fail, leaving the node stuck in a "reboot required" state. source
  • Choose a reboot time window Set the days and hours when kured is allowed to reboot, using the node's time zone. Without a window, reboots can happen whenever an update marks the system as needing one, interrupting services at inconvenient times. source
  • Add blockers for important workloads Tell kured to pause reboots while certain important pods (single app containers in Kubernetes) or active monitoring alerts are present. If you skip this, kured may restart a node while key services are running and cause avoidable downtime. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does kured know a Kubernetes node needs to be rebooted?

It watches for a reboot sentinel file such as /var/run/reboot-required or the successful run of a sentinel command.

How does kured prevent multiple nodes from rebooting at the same time?

It uses a lock in the API server so only one node reboots at a time.

Can kured avoid rebooting while alerts or certain pods are active?

Yes, it can optionally defer reboots when active Prometheus alerts or selected pods are present.

Why is there no latest tag for production use?

Using latest for production deployments is considered bad practice. The manifest on main uses latest only for local development testing with minikube; production should choose a versioned manifest.

Answers sourced from kured.dev, kured.dev

Community

Collected 48 days ago - public community threads