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

-1 non-binding My concerns echo Bob’s. There is a ton to like about k3s. There is a super enthusiastic user community and it has pioneered bringing together an opinionated set of components

-1 non-binding. I’m deeply concerned about the idea that CNCF is accepting what appears to be a Kubernetes fork into sandbox. The statements about “encouraging upstream” seem like good

+1 binding. -alena.

+1

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

+1 NB

+1 NB Ken Owens Vice President Software Development Engineering Mastercard

+1 NB Thanks & Regards, Siddharth Bhadri Software Engineer Infoblox | Next Level Networking sbhadri@... | www.infoblox.com From: <cncf-toc@...> on behalf of Lorenzo Fontana

+1 nb

+1 nb

+1 nb

+1 NB

+1 nb Phil Estes

+1 nb vote :) Barak Stout

+1 nb -- Roger Klorese Senior Product Manager, SUSE CaaS Platform SUSE +1 206 217 7432 office +1 425 444 5493 mobile roger.klorese@... 255 King Street Suite 800 Seattle WA 98104

k3s has applied for inclusion into the sandbox: https://github.com/cncf/toc/pull/447. Liz Rice has called for the vote: https://lists.cncf.io/g/cncf-toc/message/5081 Please vote (+1/0/-1) by replying

Hi everyone, At our last Sandbox application review meeting, TOC didn't vote on k3s pending a discussion with the K8s Steering Committee on whether k3s makes more sense as a standalone project or as