[Sandbox] k0s #125
Comments
|
As a representative of Replicated, I'd like to express our support for the k0s project's application to join the CNCF as a sandbox project.
Given our positive experience with k0s and its unique features, we strongly support its inclusion in the CNCF and look forward to its continued development and adoption within the wider community. |
|
Do you have a list of third party dependencies for k0s? |
|
@caniszczyk I'm not sure what you mean here by 3rd party dependencies? As for any Golang project, our Golang dependencies are managed via go modules: https://github.com/k0sproject/k0s/blob/main/go.mod The components we embed as binaries are: runc, containerd, Kubernetes (api-server, controller-manages, scheduler, kubelet), kine, etcd, iptables and keepalived We also produce SBOM for all the releases: https://github.com/k0sproject/k0s/releases/download/v1.30.4%2Bk0s.0/spdx.json As for Kubernetes itself, it still has some "3rd party" dependencies, i.e. it does call some tools on the host like |
|
@jnummelin this is exactly what I need, essentially we need the runtime dependencies and their associated licenses to ensure they are compliant with CNCF's IP Policy: https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md |
|
ok, I've checked the dependency data (attached in CSV format). All the golang modules adhere to the CNCF policy. Some of the embedded binaries, iptables and keepalived, are GPLv2, but IMO they go into this category from the policy: In this case we get the sources for those components directly from upstream repos, build them and "just" include the binary. Here is an example how we do it for iptables, all other components follow the same pattern. |
|
Per @jnummelin: On Oct 27th k0s crossed another threshold in adoption. We crossed the threshold of seeing 400k unique1 clusters throughout the telemetry collection period starting March 2021. Couldn't be more proud of the k0s team for making k0s what is is today and the dedication to make it better every day. Onwards and upwards! Footnotes
|
|
Replicated recently shared a YouTube video with more details on their use case as well as additional k0s proof points. |
|
@randybias and team, thanks for your submission! I have a couple of questions:
thanks! |
|
TAG Contributor strategy has reviewed this project and found the following:
This review is for the TOC’s information only. Sandbox projects are not required to have full governance or contributor documentation. |
We're setting all this up in a centralized community repo.
There is an organized effort to broaden the set of folks who are regular committers by adding personnel to the Open Source Program Office team here at Mirantis which one of the two major maintainer companies to the k0s project. Beyond this the regular community calls have invited contributions externally on issues of focus and there are equal efforts behind k0s (known) users requesting them to contribute on issues they have raised time to time.
kubernetes/kubernetes#96115, example of getting rid of dependencies in k8s to better align with k0s goal of "zero dependencies". |
|
Here's an example of an end user in the k0s-dev channel on Kubernetes slack thanking the k0s team for help with getting k0s working with a non-default configuration using NATS and Cilium: https://kubernetes.slack.com/archives/C07VAPJUECS/p1736700692754159 |
|
We just merged the (draft) GTR and security self-assessment docs into the main repo: https://github.com/k0sproject/k0s/tree/main/cncf |
|
thanks @randybias and @jnummelin Also, did you all get a chance to review the telemetry policy for LF projects? |
|
@dims Is that something that needs to be tackled BEFORE the sandbox phase or can it be handled while in sandbox? |
|
@jnummelin while in a the sandbox is fine. just surfacing it so you are not surprised. |
|
k0s presented to TAG-Runtime on Dec. 19th, 2024: https://www.youtube.com/watch?v=X_i2XIAqKLE |
|
/vote |
Vote created@mrbobbytables has called for a vote on The members of the following teams have binding votes:
Non-binding votes are also appreciated as a sign of support! How to voteYou can cast your vote by reacting to
Please note that voting for multiple options is not allowed and those votes won't be counted. The vote will be open for |
|
@kevin-wangzefeng to followup |
|
from this link: https://www.nops.io/blog/k0s-vs-k3s-vs-k8s/ Shared in the description as example of relevant comparison between k0s, k3s and k8s.
|
My bad. Should have read the entire thing. Removed it. |
|
The TOC has reviewed the project for sandbox inclusion and suggests the following:
|
|
/check-vote |
Vote statusSo far Summary
Binding votes (8)
|
| User | Vote | Timestamp |
|---|---|---|
| adamancini | In favor | 2025-01-14 16:50:55.0 +00:00:00 |
| laverya | In favor | 2025-01-14 16:56:24.0 +00:00:00 |
| grantmiller | In favor | 2025-01-14 16:57:43.0 +00:00:00 |
| Skaronator | In favor | 2025-01-14 17:09:55.0 +00:00:00 |
| ajp-io | In favor | 2025-01-14 17:23:07.0 +00:00:00 |
| AmberAlston | In favor | 2025-01-14 17:32:47.0 +00:00:00 |
| tzabbi | In favor | 2025-01-14 17:42:27.0 +00:00:00 |
| jtuchscherer | In favor | 2025-01-14 18:17:57.0 +00:00:00 |
| ramessesii2 | In favor | 2025-01-14 20:16:17.0 +00:00:00 |
| pschichtel | In favor | 2025-01-14 22:15:33.0 +00:00:00 |
| iggy | In favor | 2025-01-14 22:27:48.0 +00:00:00 |
| danielr1996 | In favor | 2025-01-14 22:38:20.0 +00:00:00 |
| wagnst | In favor | 2025-01-14 23:22:39.0 +00:00:00 |
| randybias | In favor | 2025-01-15 0:19:01.0 +00:00:00 |
| CmdrSharp | In favor | 2025-01-15 1:11:28.0 +00:00:00 |
| serbrech | In favor | 2025-01-15 2:45:41.0 +00:00:00 |
| bnallapeta | In favor | 2025-01-15 3:21:25.0 +00:00:00 |
| ferama | In favor | 2025-01-15 6:19:40.0 +00:00:00 |
| prithvi1307 | In favor | 2025-01-15 6:38:15.0 +00:00:00 |
| Pogyeah | In favor | 2025-01-15 7:13:20.0 +00:00:00 |
| Faithcaio | In favor | 2025-01-15 7:47:11.0 +00:00:00 |
| jnummelin | In favor | 2025-01-15 9:45:26.0 +00:00:00 |
| adityasonittyl | In favor | 2025-01-15 10:11:05.0 +00:00:00 |
| pierreozoux | In favor | 2025-01-15 11:25:48.0 +00:00:00 |
| iapicca | In favor | 2025-01-15 12:29:13.0 +00:00:00 |
| danmx | In favor | 2025-01-15 12:56:12.0 +00:00:00 |
Vote closedThe vote passed! 🎉
Summary
Binding votes (10)
|
| User | Vote | Timestamp |
|---|---|---|
| @adamancini | In favor | 2025-01-14 16:50:55.0 +00:00:00 |
| @laverya | In favor | 2025-01-14 16:56:24.0 +00:00:00 |
| @grantmiller | In favor | 2025-01-14 16:57:43.0 +00:00:00 |
| @Skaronator | In favor | 2025-01-14 17:09:55.0 +00:00:00 |
| @ajp-io | In favor | 2025-01-14 17:23:07.0 +00:00:00 |
| @AmberAlston | In favor | 2025-01-14 17:32:47.0 +00:00:00 |
| @tzabbi | In favor | 2025-01-14 17:42:27.0 +00:00:00 |
| @jtuchscherer | In favor | 2025-01-14 18:17:57.0 +00:00:00 |
| @ramessesii2 | In favor | 2025-01-14 20:16:17.0 +00:00:00 |
| @pschichtel | In favor | 2025-01-14 22:15:33.0 +00:00:00 |
| @iggy | In favor | 2025-01-14 22:27:48.0 +00:00:00 |
| @danielr1996 | In favor | 2025-01-14 22:38:20.0 +00:00:00 |
| @wagnst | In favor | 2025-01-14 23:22:39.0 +00:00:00 |
| @randybias | In favor | 2025-01-15 0:19:01.0 +00:00:00 |
| @CmdrSharp | In favor | 2025-01-15 1:11:28.0 +00:00:00 |
| @serbrech | In favor | 2025-01-15 2:45:41.0 +00:00:00 |
| @bnallapeta | In favor | 2025-01-15 3:21:25.0 +00:00:00 |
| @ferama | In favor | 2025-01-15 6:19:40.0 +00:00:00 |
| @prithvi1307 | In favor | 2025-01-15 6:38:15.0 +00:00:00 |
| @Pogyeah | In favor | 2025-01-15 7:13:20.0 +00:00:00 |
| @Faithcaio | In favor | 2025-01-15 7:47:11.0 +00:00:00 |
| @jnummelin | In favor | 2025-01-15 9:45:26.0 +00:00:00 |
| @adityasonittyl | In favor | 2025-01-15 10:11:05.0 +00:00:00 |
| @pierreozoux | In favor | 2025-01-15 11:25:48.0 +00:00:00 |
| @iapicca | In favor | 2025-01-15 12:29:13.0 +00:00:00 |
| @danmx | In favor | 2025-01-15 12:56:12.0 +00:00:00 |
| @emosbaugh | In favor | 2025-01-15 17:29:48.0 +00:00:00 |
| @p5ntangle | In favor | 2025-01-15 23:34:19.0 +00:00:00 |
|
Congrats! |
github-project-automation
bot
moved this from 🤔 In voting
to ✅ Done
in Sandbox Application Board
Application contact emails
jnummelin@mirantis.com, rbias@mirantis.com
Project Summary
k0s is a CNCF-certified lightweight, Kubernetes distribution with zero dependencies and zero opinion.
Project Description
k0s is a fully conformant, CNCF-certified Kubernetes distribution that offers a zero-dependency, statically compiled, vanilla Kubernetes experience. Designed to run anywhere—from bare metal to cloud environments—k0s provides a minimal footprint with a low attack surface. It enforces a strong separation between controllers and workers, enhancing security and operational efficiency.
k0s aligns with the CNCF mission by fostering an open-source, vendor-neutral Kubernetes distribution that emphasizes choice and flexibility within the cloud-native ecosystem. By providing diversity of choice, k0s encourages innovation and collaboration, strengthening the Kubernetes community.
Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/k0sproject
Project repo URL in scope of application
https://github.com/k0sproject/k0s
Additional repos in scope of the application
https://github.com/k0sproject/k0sctl
Website URL
https://k0sproject.io/
Roadmap
https://github.com/k0sproject/k0s/milestones
Roadmap context
In our monthly office hours and community channels, we openly discuss roadmap items, gathering input and prioritizing items through collaborative discussions. Our approach is strongly oriented towards fostering a thriving ecosystem, and we actively seek opportunities for interoperability with CNCF projects and other open-source initiatives. This commitment helps us better address the interests and needs of our community.
We are working towards a more formal roadmap.
Contributing Guide
https://github.com/k0sproject/k0s/blob/main/docs/contributors/overview.md
Code of Conduct (CoC)
https://github.com/k0sproject/k0s/blob/main/CODE_OF_CONDUCT.md
Adopters
https://github.com/k0sproject/k0s/blob/main/ADOPTERS.md
Contributing or Sponsoring Org
https://mirantis.com
Maintainers file
https://github.com/k0sproject/k0s/blob/main/MAINTAINERS.md
IP Policy
Trademark and accounts
Why CNCF?
k0s seeks to apply to CNCF in order to find a vendor-neutral home. The k0s community has seen significant adoption and has matured rapidly, recently adding additional non-Mirantis maintainers from Replicated.com. With over 7,500 weekly active clusters in the wild that average over 300+ days in age, we believe the time is right to become an official project of the CNCF.
We want to demonstrate our commitment to managing expansion in an open-source manner and ensure neutral governance for our growing community of users and contributors. The CNCF platform will serve as an additional catalyst for community adoption and encourage contributions from developers. Additionally, being a part of CNCF allows k0s to learn from other projects and actively contribute back to the cloud-native community, aligning with the maintainer's ethos.
k0s wants to establish itself as a clear alternative k8s distribution for those who want an ultra lightweight, secure, vanilla distribution that supports all x86 and ARM platforms.
Benefit to the Landscape
The CNCF ecosystem would benefit from having additional conformant k8s distributions, especially ones with a specific niche, such as k0s: lightweight, no opinion, works anywhere and on any platform.
Key Features Include:
Cloud Native 'Fit'
k0s is about as cloud-native as you can get, given it is basically the purest and simplest form of a k8s distribution.
Cloud Native 'Integration'
Nothing besides core Kubernetes.
Cloud Native Overlap
There is some overlap with k3s, but ultimately, we believe there is a enough difference in approach to allow both distributions in the Kubernetes ecosystem.
Here are some different perspectives from around the web for this year, comparing k0s and k3s:
Perhaps more importantly, here are a couple of k0s users explaining why they preferred k0s over k3s:
Similar projects
k3s
Landscape
Yes, k0s is listed in the landscape.
Business Product or Service to Project separation
Some Mirantis products do leverage k0s, but the project is maintained completely separately from our products and has been since inception. Originally Mirantis products used other k8s distributions, but recently migrated to k0s. A close inspection of GitHub issues will show you that there is a clear firewall between k0s and our enterprise products. Putting k0s into the CNCF will further help maintain it's independence.
Project presentations
Runtime TAG in 2021:
https://www.youtube.com/watch?v=5Hja-cGXZ5Q&ab_channel=CNCFTAGRuntime
Edge/IoT WG in 2022:
https://youtu.be/L5jWfM6kn5M?t=1695
Project champions
TBD
Additional information
We collect anonymous usage data. Attached is a screenshot of our k0s dashboard with some detailed statistics showing our accelerated growth over the past year.
k0s Dashboard.pdf
The text was updated successfully, but these errors were encountered: