Re: [VOTE] Helm project proposal (incubation)
Barker, Daniel <drbarker@...>
+1 non-binding, however I’m concerned about the precedent being set of including k8s-only tools. I think this precedent was already set with Telepresence or Rook. The TOC requires a specification to be broadly adopted, so why not other tools. Should there be a requirement that before moving into incubation a project has to be usable across multiple primary platforms. I don’t think the language on that is accurate, so I’ll expand. For example, rkt is not dependent on k8s. It can run on a primary platform of k8s or a bare OS. Linkerd and Envoy can run on Mesos and VMs. In effect, the TOC is acting as a Kingmaker for k8s if it chooses to include so many k8s-only tools. These all are currently just in Sandbox, but I see nothing preventing all of them from graduating. Also, this is nothing against the projects or k8s, it’s about surfacing the disparity between the actual appearance of the CNCF and the intended or stated appearance of the CNCF. Are we unintentionally excluding projects that won’t run on k8s?
Dan Barker Chief Architect National Association of Insurance Commissioners 1100 Walnut St. Suite 1500 Kansas City, MO 64106 816-783-8669
From: cncf-toc@... <cncf-toc@...>
On Behalf Of Christian Jantz
Sent: Thursday, May 31, 2018 7:17 AM To: CNCF TOC <cncf-toc@...> Subject: Re: [cncf-toc] [VOTE] Helm project proposal (incubation)
+1
----------------------------------------- CONFIDENTIALITY NOTICE This message and any attachments are from the NAIC and are intended only for the addressee. Information contained herein is confidential, and may be privileged or exempt from disclosure pursuant to applicable federal or state law. This message is not intended as a waiver of the confidential, privileged or exempted status of the information transmitted. Unauthorized forwarding, printing, copying, distribution or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or by forwarding it to the NAIC Service Desk at help@.... |
|