Re: Cloud Native definition last call
Richard Hartmann
Nitpick: s/the approach/this approach/ Else, it looks good. Sent by mobile; please excuse my brevity.
|
|
Re: Cloud Native definition last call
Erin Boyd
I think it's perfect. Erin
|
|
Re: Cloud Native definition last call
Brian Grant
We went through many iterations, but I'm pretty happy where it has landed: --- Cloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify the approach. These techniques enable loosely coupled systems that are resilient, manageable, and observable. Coupled with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil. The Cloud Native Computing Foundation seeks to drive adoption of this paradigm by fostering and sustaining an ecosystem of open source, vendor-neutral projects. We democratize state-of-the-art patterns to make these innovations accessible for everyone. ---Thanks to everyone who helped and provided feedback.
On Sun, Apr 29, 2018 at 4:52 AM Dan Kohn <dan@...> wrote:
|
|
More Helm Information
Matt Farina
In the TOC meeting today there were a number of questions around Helm. I can add a little more context and some links. If there additional questions please feel free to ask.
Helm Inspiration
When it comes to Helms scope it might be useful to look at Debian Apt. Helm is inspired by apt in many ways. For example, anyone can run a repository and you can have more than one of them. This means we can have static repos, open source projects that implement push/pull servers, and proprietary projects (jFrog Artifactory) that can all be registries. Another example is the way it can be used in corporate environments with mirrors, internal projects, and so forth.
While implementation details will vary because of the nature of the platform, the same types of features you can find in apt are found in Helm.
Kubernetes Focus
There were questions around what's owned by the Kubernetes project. Brian can add more context than I can but the short version is that the Kubernetes project is focusing on core Kubernetes rather than projects that sit on top of it or around it. Something like Helm would not be considered to be part of the Kubernetes project if it were a decision today. Numerous things around Kubernetes have been proposed recently and the guidance was to do them in the ecosystem.
Kubernetes, as a project, is attempting to focus on core Kubernetes. It provides a boundary where the project can handle managing itself and not try to manage too many things.
Helm and other package managers
The Kubernetes project doesn't want to bless any one project or way of doing things when it comes to that which is beyond core Kubernetes. This includes package management, developer tools, and so forth. There is a goal to allow and even enable a competitive landscape. This has even lead to asks of moving Helm out of Kubernetes to help Kubernetes be less biased.
Along with that, a platform can have multiple package managers. For example, ubuntu has both apt and snaps. The experience around those can be quite different and that's OK.
When it comes to the numbers, Helm is the package manager people use. Kubepack, the package manager Brian brought up on the call, only showed up once on the Kubernetes Application Survey. When Helm was gaining traction there was KPM competing against it. KPM had a lot of potential and good ideas. Helm gained far more traction and now KPM is no longer maintained.
At the moment there are no other package managers competing with Helm that have traction. That's not to say what will happen but rather an observation of the current state.
Personally, I'm quite OK with competition because, I think, it can push competing projects to be better than if they were left on their own.
Helm and other tools
Helm is focused on the package manager problem. There's a blog post with diagrams to show how it can related to other projects. There are tools built on top of Helm such as Armada, landscaper, and helmfile. Helm isn't trying to expand into these spaces though some people are trying to bend it that way. Instead, the helm team is trying to encourage more of these projects to be used.
Helm v3
Helm v3 is currently under development and you can learn more about it in the proposal for it. Some of the design changes and the philosophy is to provide better interoperability and extension mechanisms. As the community has grown and people want to interact with various other tools we're looking to make that easier.
I'm happy to dig into more of this. You can respond here or reach out to me personally. I'm happy to help fill in any gaps.
Regards,
Matt
--
Matt Farina
Go in Practice - A book of Recipes for the Go programming language.
Code Engineered - A blog on cloud, web, and software development.
|
|
TOC Agenda 5/15/2018
Here's the agenda for tomorrow's TOC meeting: We will be hearing from the CloudEvents and Helm projects along with some updates from the various CNCF Working Groups. We will also have time to take feedback from the TOC and wider community on how kubecon/cloudnativecon went but feel free to leave that feedback on this list, thanks. Thanks! Chris Aniszczyk (@cra) | +1-512-961-6719
|
|
Re: Updates and next toc call
Brandon Philips <bphilips@...>
The Operator Framework was launched: We have also started tracking Operators here:
On Mon, May 7, 2018 at 2:20 AM alexis richardson <alexis@...> wrote: Hi all
|
|
Re: Updates and next toc call
udi@...
Cloud 66 announced Formations and Stencils in GA, alongside Copper (open source): https://blog.cloud66.com/press-release/
toggle quoted messageShow quoted text
udi@... | M. +44 7769 235 135
|
|
Re: Updates and next toc call
Mark Coleman <mark@...>
Dotmesh announced the Dotmesh Kubernetes Operator: https://dotmesh.com/blog/dotmesh-operator/
On Mon, May 7, 2018 at 10:21 AM alexis richardson <alexis@...> wrote: Hi all --
|
|
Re: Updates and next toc call
Craig Peters
JFrog announced Artifactory integrations with SUSE CaaSP, Canonical Distribution of Kubernetes, and Bitnami Kubeapps
On Thu, May 10, 2018 at 9:40 AM Richard Li <richard@...> wrote:
--
Craig Peters | Director of Product, Partners | JFrog http://www.jfrog.com | m: +1 925-639-0804 | skype: craig.l.peters ![]()
|
|
Re: Updates and next toc call
Richard Li
Datawire announced Ambassador 0.32, with support for traffic shadowing: https://blog.getambassador.io/announcing-ambassador-0-32-af1b68548b1a. ![]() ![]()
On Wed, May 9, 2018 at 10:41 AM, Sebastien Goasguen <sebgoa@...> wrote:
|
|
Re: Updates and next toc call
Sebastien Goasguen <sebgoa@...>
Bitnami announced: kubeapps 1.0.0 (including support for service broker with MSFT and Jfrog Artifactory) and kubeless 1.0.0 (including support for cloudevents 0.1.0 in cooperation with SAP, demo at #kubecon).
On Wed, May 9, 2018 at 4:31 PM, Raphaël Pinson <Raphael.pinson@...> wrote:
--
Sebastien Goasguen Senior Director of Cloud Technologies, Bitnami +41 79 367 38 25 @sebgoa
|
|
Re: Updates and next toc call
Raphaël Pinson
Hello, Not sure if relevant as this was not announced AT Kubecon, but it was announced during Kubecon and with the #kubecon hashtag on Twitter:https://camptocamp.github.io/bivac/
On Mon, May 7, 2018 at 11:25 AM, Paul Fremantle <paul@...> wrote:
--
Raphaël Pinson Infrastructure Developer & Training Leader +33 458 482 013
Camptocamp France SAS Bâtiment le Dauphin - 1er étage 18 rue du Lac Saint André Savoie Technolac F-73370 Le Bourget du Lac
|
|
Re: Updates and next toc call
JJ
SAFE had a good reception overall. Several people were genuinely concerned about understanding and describing the end-end security. Here are the session links:
On Mon, May 7, 2018 at 11:58 AM, alexis richardson <alexis@...> wrote: Excellent - thanks.
|
|
Re: Updates and next toc call
alexis richardson
Excellent - thanks.
toggle quoted messageShow quoted text
On Mon, May 7, 2018 at 7:47 PM, Ken Owens <kenchristineowens@...> wrote:
We would like to update the TOC next week on the TOC call.
|
|
Re: Updates and next toc call
Ken Owens
We would like to update the TOC next week on the TOC call.
On Mon, May 7, 2018, 6:24 AM alexis richardson <alexis@...> wrote: Sugu
|
|
Re: Updates and next toc call
Yaron Haviv <yaronh@...>
FYI.. TheCube Video interview of Doug (IBM) & me on Serveless & CNCF Serverless WG activities: https://www.youtube.com/watch?v=5S8C009i4lo
Coverage w mention of CNCF Serverless-wg/cloudevents:
Serverless computing takes a big step into the multicloud world https://siliconangle.com/blog/2018/05/03/serverless-computing-takes-big-step-multicloud-world/
Serverless framework Nuclio released for enterprise customers https://thestack.com/cloud/2018/05/02/serverless-framework-nuclio-released-for-enterprise-customers/
From: <cncf-toc@...> on behalf of alexis richardson <alexis@...>
Hi all
Kubecon was excellent. A few things:
* If you made an announcement, gave a talk or posted a blog about kubecon that is relevant to TOC business (including WGs) please could you publish a link on this thread? Eg azure cloudevents.
* Quinton is the new TOC representative in the Storage WG. Many thanks to Ben for getting us to here, and Clint for all his work too. Also Camille for helping Quinton and the SWG shape next steps. And: anyone else I missed!
* Let's have a quick round up on all this and other news on the next TOC call.
A
|
|
Re: Updates and next toc call
alexis richardson
Sugu
toggle quoted messageShow quoted text
Thanks. Would be great to get some of that over to cncf marketing (cc'd Dee) if not already done ... For the TOC I think key points are: - project progress and health - interlock with SWG if any - interoperability news
On Mon, 7 May 2018, 14:21 Sugu Sougoumarane, <ssougou@...> wrote:
|
|
Re: Updates and next toc call
Sugu Sougoumarane
Not sure what's relevant to TOC, but I weaved a few Vitess announcements through the keynote presentation: - Vitess won the MySQL Community Awards for "Application of the Year 2018". - Coincidental co-announce about JD.com: they have the largest deployment of Vitess in production on kubernetes. - Prometheus support. - New helm charts and an operator.
On Mon, May 7, 2018 at 6:05 AM, Doug Davis <dug@...> wrote:
|
|
Re: Updates and next toc call
Doug Davis <dug@...>
Yup - already in plan
thanks -Doug _______________________________________________________ STSM | IBM Open Source, Cloud Architecture & Technology (919) 254-6905 | IBM 444-6905 | dug@... The more I'm around some people, the more I like my dog
----- Original message -----
|
|
Re: Updates and next toc call
alexis richardson
Great, please could you work with Ken, and pull in the other serverless WG folks, to create an update for next TOC?
toggle quoted messageShow quoted text
On Mon, 7 May 2018, 11:19 Yaron Haviv, <yaronh@...> wrote:
|
|