I'm probably jumping into the conversation uninformed and without context. I just want to make it very clear k3s is in no way shape or form a fork. There is nothing technically correct about calling

+1, binding.

Per Bob's point 3, k3s want a neutral home for further experimentation and collaboration; in my opinion it is undoubtedly cloud native, and it solves a particular problem in a way that lots of folks

K3s is a distro, and it is a fork as well. The "opinionated" description always applies to distros (which can be more or less opinionated, of course). If the opinion included things like backported

Abstain Unfortunately I missed the "Joint CNCF TOC/Kubernetes Steering Committee" meeting. But I talked to some folks afterwards to fill me in. Overall, I'd like to avoid setting precedent that a

+1, NB

+1 nb From: <cncf-toc@...> on behalf of "Phil Estes via lists.cncf.io" <estesp=gmail.com@...> Reply to: "estesp@..." <estesp@...> Date: Friday, 31. July 2020 at 17:13 To: "cncf-toc@..."

+1 binding On Aug 2, 2020 12:13 AM, "Liz Rice via lists.cncf.io" <liz=lizrice.com@...> wrote: +1 binding On Sat, 1 Aug 2020 at 09:22, Richard Hartmann <richih@...> wrote:

+1 binding

+1 NB 发自 WPS邮箱客戶端 在 Mofei Zhang <mofei2816@...>，2020年8月1日 19:34写道：

+1 NB Mofei Zhang Architect , JD.com Maintainer , ChubaoFS

+1 NB I see it as a learning tool, which has merit in and as of itself. Similar to how Cortex and Thanos help shape the future for Prometheus, k3s can act as a canonical proving ground of sorts

+1 nb I appreciate that the TOC took the time to talk with the Kubernetes Steering Committee prior to calling for a vote. I can't imagine a vote moving forward without their blessing. It's great that

Big fan of k3s! +1 NB -- Christian Posta twitter: @christianposta http://blog.christianposta.com

+1 binding I think this is an opportunity for us to create forums/feedback loops and improve communication between distribution like projects and core projects where it makes sense. If Kind or

Currently k3s is a distro of k8s. We used to have a k8s sandbox. If we still did then k3s would happily live there as a way to show k8s how to be a better project.

+1 nb

k3s is not a fork of Kubernetes. It is an opinionated way of delivering Kubernetes to IoT and Edge devices. Talking to Kubernetes steering committee made it clear that Kubernetes main design principle

-1 NB for the same reasons echoed above. I would be quiet since there seemed to be a large consensus to accept it, but it seems like a poor precedent. Similarly, I feel that Thanos and Cortex are

-1, nb +1 to joe & bob comments. I am very keen to see k3s initiative do well I am even more keen to see it feed back into K8s let's find a way to make this work! I don't know the answer and