k3s-io/k3s-upgrade

k3s-upgrade is a container image that performs in-place upgrades of k3s clusters through the System Upgrade Controller.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

k3s-io/k3s-upgrade has 100+ stars and 40+ forks on GitHub, is written in Shell, and was last pushed on Sep 30, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on January 27th, 2020
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 40
Total Stargazers: 148 (+0)
Total Subscribers: 5 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

k3s-upgrade is a container image that performs in-place upgrades of k3s clusters through the System Upgrade Controller.

The tool solves the problem of upgrading k3s versions in a controlled, automated manner. It works by replacing the k3s binary with a new version and then terminating the old k3s process, allowing the supervisor to restart the service with the updated binary. This approach integrates with the System Upgrade Controller, which orchestrates the upgrade process across nodes in the cluster.

Adoption requires k3s to have been installed using the official install script via curl. The workflow involves deploying the System Upgrade Controller to the cluster, labeling the nodes intended for upgrade, and then creating an upgrade plan that the controller watches and executes. This suits teams running k3s who want automated, coordinated upgrades across multiple nodes rather than manual per-node updates. The tool is purpose-built for k3s and depends on the System Upgrade Controller framework for orchestration and scheduling.

Development activity is minimal, with the codebase consisting primarily of shell scripting for the upgrade mechanics.