k3s-io
/
k3s
mirror of https://github.com/k3s-io/k3s.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update ROADMAP.md to show that we track upcoming features/fixes in GH (#12477) 

* Update ROADMAP.md to show that we track upcoming features/fixes in GitHub milestones using GitHub projects, to keep it up to date

Signed-off-by: Chris Wayne <cwayne18@gmail.com>
pull/12580/head
Chris Wayne 2025-07-02 13:02:14 -04:00 committed by GitHub
parent e6e301959f
commit 338b9cc923
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
ROADMAP.md
View File

@ -1,17 +1,7 @@
Roadmap
---
This represents the larger, bigger impact features and enhancements we have planned for K3s. Features are planned, but do not represent a commitment to develop and can change at any time. There are many more tactical enhancements and fixes that can be found by reviewing our [GitHub milestones](https://github.com/k3s-io/k3s/milestones).
The k3s project uses [GitHub Milestones](http://github.com/k3s-io/k3s/milestones) to track the progress of changes going into the project.
Next
---
- Embedded registry support
- Windows OS Support
Later
---
- Multus CNI support
- Align K3s with upstream Kubernetes by removing patches or upstreaming them
- FIPS-140-2 Compliant binaries
- Graduate encrypted networking support from experimental to GA
- Graduate network policy support from experimental to GA
The k3s release cycle moves in cadence with upstream Kubernetes, with an aim to have new minor releases out within 30 days of upstream .0 releases. To follow incoming changes, watching the [Backlog](https://github.com/orgs/k3s-io/projects/5) and [Current Development](https://github.com/orgs/k3s-io/projects/6) GitHub Projects is the most up to date way to see what's coming in upcooming releases.
The development of k3s itself happens in the `master` branch, which correlates to the most recent Kubernetes minor release. These changes are then backported to the active release lines (at this time, `release-[N]`, `release-[N-1]`, and `release-[N-2]`)