+1 NB

+1 binding

-1 NB ... from a security perspective, i cant up vote this project despite my appreciation - at this point I am concerned on how a fork maintain security patches of mainline k8s. -- Gadi

Hi all, We'll be meeting tomorrow with a SIG update meeting. Agenda: https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit# Presentation:

+1 NB JINYONG KIM | 김진용 CEO | 대표이사 NexCloud http://www.nexcloud.co.kr http://www.nexclipper.io O 02-533-8622 M +82 10-2048-8697 F 02-533-8623 06192 서울특별시

+1 non-binding Jimmy Song https://jimmysong.io

+1 binding k3s has made it clear that it is not a fork and that is not the road it is going down. It is a distro, and I feel that distros are valuable work in open source, with many examples. The

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