/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

k3s-io/k3s

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T15:58:50.414Z

1mo ago

k3s-io/k3s

k3s-io/k3s is a lightweight Kubernetes distribution: production-ready, fully conformant, packaged as a single binary, and aimed at edge, IoT, CI, development, ARM, and embedded use cases. It is very active, with a large community footprint (32,611 stars, 2,631 forks) and recent commits as of 2026-03-30.

Loading tags...

Stars32,611

Forks2,631

Default branchmain

Last pushed2026-03-30T14:28:32Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer upstream k3s unless you explicitly need this fork's custom behavior and can own the long-term maintenance burden. This fork looks suitable only for narrow, internal use cases where its bespoke changes matter more than freshness, security, or upstream compatibility.

Prefer this fork if you need its local workflow and operational changes and are prepared to absorb upstream lag. Prefer upstream k3s if you want the newest fixes, simpler maintenance, and less divergence risk.

Prefer upstream K3s unless you specifically need this fork's local changes. This fork looks like a stale, materially diverged branch with custom test and runtime behavior, so adopters should expect extra maintenance burden and missed upstream fixes.

Choose this fork only if its distro-install compatibility or killall behavior matches a hard requirement. For most adopters, upstream k3s is the safer default because this fork is materially stale and likely missing a large amount of recent fixes and release work.

Choose this fork only if you need its specific legacy operational tweaks. For most adopters, upstream K3s is the safer default because this fork is stale, materially behind, and likely missing many later fixes and releases.

Prefer upstream K3s unless you specifically need this fork's legacy installer and cluster-management tweaks. Adopt this fork only if you are intentionally pinning to its older behavior and can accept missing modern upstream fixes and releases.

Choose upstream unless you explicitly need this fork's legacy installer and SELinux-oriented changes. For most adopters, the maintenance risk and age of the fork outweigh its limited customizations.

Adopt only if you specifically need this exact upstream snapshot. For most users, upstream K3s is the better choice because this fork adds no clear capability and is already behind recent upstream fixes.

Choose this fork only if you explicitly want an older, unchanged k3s baseline. For most adopters, upstream is the better choice because this fork adds nothing and lags behind recent fixes and updates.

Prefer this fork only if its specific fixes match your needs and you are comfortable owning an aging, diverged K3s codebase. For most adopters, upstream K3s is the safer choice because this fork is stale and materially behind.

Fork comparison

fastlorenzo/k3s

38/100

stale

significant_divergence

Prefer upstream k3s unless you explicitly need this fork's custom behavior and can own the long-term maintenance burden. This fork looks suitable only for narrow, internal use cases where its bespoke changes matter more than freshness, security, or upstream compatibility.

Likely purpose

A personal or niche downstream branch for experimenting with k3s internals and test infrastructure rather than a general-purpose upstream replacement.

Best for

Operators who need a frozen, customized k3s variant for a specific lab or internal environment.; Developers investigating or maintaining fork-specific etcd, netpol, or servicelb changes.; Users who value local modifications over staying current with upstream k3s releases.

Additional features

Custom changes in etcd management and snapshot handling suggest altered datastore behavior or recovery workflows.
Custom network policy logic in `pkg/agent/netpol/policy.go` suggests fork-specific netpol behavior.
Changes in `pkg/cloudprovider/servicelb.go` suggest service load balancer behavior was modified.
Large integration-test and test harness changes suggest the fork may support a different validation or deployment workflow.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

It is far behind current upstream k3s releases, so it likely lacks newer Kubernetes, Flannel, Helm-controller, Trivy, and Go updates present upstream.
Upstream's recent bug fixes, security updates, and dependency refreshes are not being tracked.
Deletion-heavy changes in integration/test assets suggest some upstream validation coverage or example workflows were removed or made harder to use.
Because the fork stopped pushing in 2022, adopters should assume many upstream improvements in operational tooling and packaged components are missing.
It trails upstream by 225 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

May be useful if you specifically need the fork's etcd, netpol, or servicelb customizations.
Could fit controlled environments where a frozen k3s baseline is preferable to frequent upstream churn.
Large test and workflow edits suggest someone was actively adapting the project for their own CI or lab setup.

Risks

High upgrade risk because the fork is stale and substantially behind upstream.
Large divergence makes rebasing or backporting upstream fixes expensive.
Security and stability risk is elevated because recent upstream fixes are not being incorporated.
The fork's purpose is not obvious from the metadata, so operational expectations are hard to predict.