Proposal: Cilium as an Incubation project #637
Conversation
See markdown file included in commit for details on proposal. Signed-off-by: Thomas Graf <thomas@cilium.io>
tgraf
changed the title
|
Awesome! FYI: @cncf/toc, I believe @justincormack has volunteered to be TOC sponsor |
|
Yes, I have agreed to sponsor. I will also liaise with SIG Network cc @leecalcote |
amye
moved this from Needs TOC Triage
to Needs SIG Review & Recommendation
in Incubation Projects Backlog
amye
moved this from Needs TAG Review & Recommendation
to In Due Diligence
in Incubation Projects Backlog
|
DD summary document is here https://docs.google.com/document/d/1PlDiCA58nZEJGfWw32R-Y1cGI02ZUhQa6KG8ueSpef8/edit I am opening the two week public comment period now. https://lists.cncf.io/g/cncf-toc/message/6063 |
amye
moved this from In Due Diligence
to In Public Comment Period
in Incubation Projects Backlog
|
...not now the eBPF Foundation? https://www.linuxfoundation.org/press-release/facebook-google-isovalent-microsoft-and-netflix-launch-ebpf-foundation-as-part-of-the-linux-foundation/ (emphasis mine):
|
|
@craigbox We'll stick with the CNCF 馃槃. Given the cloud native focus of Cilium, CNCF is the ideal home for Cilium. The eBPF foundation has been created to facilitate the eBPF technology more broadly, in particular the kernel runtimes, the libraries, and other toolkit projects. |
amye
moved this from In Public Comment Period
to In TOC Vote
in Incubation Projects Backlog
Hello TOC and CNCF community 馃憢
We are proposing Cilium to become a CNCF project at Incubation level.
What is Cilium?
Cilium is an open source project for providing and transparently securing network connectivity, and loadbalancing between application workloads such as application containers or processes. Cilium operates at Layer 3/4 to provide traditional networking and security services as well as Layer 7 to protect and secure use of modern application protocols such as HTTP, gRPC and Kafka. Cilium implements the Container Networking Interface (CNI) and integrates directly with Kubernetes.
A new Linux kernel technology called eBPF is at the foundation of Cilium. It supports dynamic insertion of eBPF bytecode into the Linux kernel at various integration points such as: network IO, application sockets, and tracepoints to implement security, networking and visibility logic. eBPF is highly efficient and flexible. (To learn more about eBPF, visit eBPF.io.)
Why we chose the CNCF?
Moving an already big open-source project into a foundation is not a simple decision. We have grown organically to a sizable community of 6K slack users, 7.9K GitHub stars, well beyond 200 direct code contributors, maintainers from 8 different companies, and a long list of large-scale production users.
When we started the project, we all agreed that we would wait with any foundation discussion until users would urge us to have the discussion with a justification that makes sense for the project. In the last couple of months, this has happened. The list of users approaching us and requesting to donate Cilium to a foundation has skyrocketed. As we dug deeper into the motivation for the ask, we learned that everyone agrees that the governance and development models are already fully open and following open-source best practices. However, the final piece of commitment to this model is the donation to an independent foundation. For many users, the donation is the last piece of insurance required before committing to large projects built on Cilium and resolves a variety of risks related to depending on the agenda of any particular single vendor. This motivation makes sense for us as a team. We understand and share it.
We (the Cilium team) believe the CNCF is a great fit for Cilium as the mission of the CNCF the goals of the Cilium open-source project are extremely well aligned. The core focus of Cilium is to provide networking and security for cloud-native environments. Logically, we have integrated deeply with projects like Kubernetes, etcd, Prometheus, and Envoy.
With 鉂わ笍, the Cilium Team