The TOC has decided to invite containerd (http://containerd.io/) as an incubation level CNCF project, sponsored by Brian Grant from the TOC: containerd is a widely used container runtime with an

We're almost sold out: https://twitter.com/CloudNativeFdn/status/844602672636321792 Please register today and I hope to see many of you in

Non-binding, but +1 to both! thanks -Doug _______________________________________________________ STSM | IBM Open Source, Cloud Architecture & Technology (919) 254-6905 | IBM 444-6905 |

All, please do take a look!

Hey CNCF TOC and wider community, we have two project proposals in queue: containerd: https://github.com/cncf/toc/pull/32 rkt: https://github.com/cncf/toc/pull/33 Please look them over on GitHub and

> It's important for CNCF to own and foster the foundational technology for cloud-native computing. Having both containerd and rkt in CNCF would be a great outcome for the CNCF, for Kubernetes, and

CF runs on a CaaS called Diego, it's just not very well known or used with non-CF systems. Kubernetes arguably supports more use cases already eg Openshift PaaS, and then others. I do think that,

>>What I did find interesting however is that Pivotal and CloudFoundry are explicitly and publicly supporting Kubernetes, so hopefully that means that porting CloudFoundry apps and tools to Kubernetes

Ziad, since you mentioned Docmer here is my take on your question. The type of convergence we're seeing is Kube+containerd and cloudfoundry+containerd. With the donation of containerd to CNCF

Regarding Kubo, it’s not immediately obvious to me how useful it is in the long term (although I must stress that I’m definitely not a Cloud Foundry expert). Reading the Kubo docs it seems that

which one of those is brownfield? ;-)

Low friction, low switching cost....interesting topics. How we manage the large "brownfield" estate is a big challenge. What I am interested in seeing is how PCF+Kube+Docker evolves and how RH

The lowest friction adoption path for CNCF technologies in the CF community is via add-ons, accessed via the CF service broker mechanism. Kubo is a step in that direction because existing CF

Hi All, seen this? what is everyone’s view? Thanks Ziad ============================================================================== Please access the attached hyperlink for an important

+Karthik to make sure he sees these emails as a chance to give feedback. If I recall from the call that was a question that BrianG may have asked. Karthik mentioned some things of why CNCF (vs other

I would echo Brian's sentiments - I also have some concerns about Heron's cloud-native suitability and path to integration with any of the existing or proposed CNCF projects; I think it's still hard

Moving Heron to new thread. All - comments on Heron? I think Brian raises some good questions about alignment with our mission (below).

Brian Your offer is most welcome. Let's follow up with the project leads to request a document with their full proposal, and explore timing. Alexis

+1 for containerd and rkt. I don’t know enough about Heron and the related ecosystem to have an on that opinion yet. Q From: <cncf-toc-bounces@...> on behalf of Brian Grant via cncf-toc

I'd like to sponsor both containerd and rkt. It's important for CNCF to own and foster the foundational technology for cloud-native computing. Having both containerd and rkt in CNCF would be a great