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

General updates to README (#8786) 

Signed-off-by: Derek Nola <derek.nola@suse.com>
pull/8863/head
Derek Nola 2023-11-15 09:45:29 -08:00 committed by GitHub
parent 19fd7e38f6
commit 78ea593780
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -46,7 +46,7 @@ Additionally, K3s simplifies Kubernetes operations by maintaining functionality
* Managing the TLS certificates of Kubernetes components
* Managing the connection between worker and server nodes
* Auto-deploying Kubernetes resources from local manifests in realtime as they are changed.
* Managing an embedded etcd cluster (work in progress)
* Managing an embedded etcd cluster
Current Status
--------------
@ -103,12 +103,12 @@ Release cadence
K3s maintains pace with upstream Kubernetes releases. Our goal is to release patch releases within one week, and new minors within 30 days.
Our release versioning reflects the version of upstream Kubernetes that is being released. For example, the K3s release [v1.18.6+k3s1](https://github.com/k3s-io/k3s/releases/tag/v1.18.6%2Bk3s1) maps to the `v1.18.6` Kubernetes release. We add a postfix in the form of `+k3s<number>` to allow us to make additional releases using the same version of upstream Kubernetes while remaining [semver](https://semver.org/) compliant. For example, if we discovered a high severity bug in `v1.18.6+k3s1` and needed to release an immediate fix for it, we would release `v1.18.6+k3s2`.
Our release versioning reflects the version of upstream Kubernetes that is being released. For example, the K3s release [v1.27.4+k3s1](https://github.com/k3s-io/k3s/releases/tag/v1.27.4%2Bk3s1) maps to the `v1.27.4` Kubernetes release. We add a postfix in the form of `+k3s<number>` to allow us to make additional releases using the same version of upstream Kubernetes while remaining [semver](https://semver.org/) compliant. For example, if we discovered a high severity bug in `v1.27.4+k3s1` and needed to release an immediate fix for it, we would release `v1.27.4+k3s2`.
Documentation
-------------
Please see [the official docs site](https://rancher.com/docs/k3s/latest/en/) for complete documentation.
Please see [the official docs site](https://docs.k3s.io) for complete documentation.
Quick-Start - Install Script
--------------

4
ROADMAP.md
View File

@ -4,14 +4,12 @@ This represents the larger, bigger impact features and enhancements we have plan
Next
---
- CLI support for etcd backup management
- Multus CNI support
- Experimental support for migration from SQLite to etcd
- 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