Cloud Native Computing Foundation KubeCon + CloudNativeCon North America 2018 (Seattle), 15 Dec 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keynote: The Unification of Containers, Apps and Functions - Jason McGee

Description

Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io

Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects

Keynote: The Unification of Containers, Apps and Functions - Jason McGee, IBM Fellow, VP and CTO, IBM Cloud Platform, IBM

Cloud-native developers today have to decide between 3 separate container platforms.  Some choose the flexibility of containers with Kubernetes, others the velocity of an opinionated platform like CloudFoundry, and still others believe the future is all about serverless functions.  How do you know which ones to use? And should you have to choose?  In this keynote, Jason McGee will share his vision for the marriage of containers, apps, and functions -- driven by Kubernetes, Istio and the emergence of Knative into a single combined container platform.  It’s time to break down the silos and see how these projects’ paths are converging to solve real microservice dilemmas: security, scale, and operations.

To learn more: https://sched.co/GsxS

A

Good morning, I started my career over 20 years ago, working on Java app servers, app servers provided a platform for developers to be able to focus on building and running their applications efficiently without having to solve all the kind of boring plumbing problems they might be saying Jason 20 years ago is a long time.

A

Why are we talking about this well I think today, this community is actually solving many of the same problems that platform challenge problem, but we're doing it together in the era of cloud now any realistic application development project, you have different requirements. They have to meet some components of your application, might be stateless, Web, Apps, some components or stateful databases. Some components are more event. Oriented some require a lot of flexibility and others are simple, and a good application platform allows you to handle all of these requirements together.

A

Now, in the cognitive space, we've been fundamentally focusing our efforts around three styles of applications on the platform that we have 12 factor, applications, functions and server lists and containers, but so far we've mostly been building these three stacks in independent ways. We've been billing.

A

Three independent separate stacks to handle general-purpose containers to handle applications and handle functions and by building them separately, we're forcing people to make choices, we're forcing developers to pick sides we're making the environments more complex and we're creating friction as developers try to mix these dissimilar Styles together now, as a community we've actually over the last few years, made a lot of progress on joining forces and agreeing on some common elements.

A

In the cloud native stack, we've taken the best of our experience and code in a variety of projects and come together around the container engine with projects like container D, we've come together with all of our learnings around orchestration and created this incredible phenomenon. The Janna just talked about around kubernetes and we've had new things like service brokers and service meshes that we've kind of quickly come together and had a common understanding of the value of those things and some of the projects we want to work on together to make them part of the stack.

A

So what's missing what about apps and functions? How do we bring apps and functions into this common view of an application platform? Now, for apps, one of the most prominent projects in the application space is quad. Foundry cod foundry is already aligned around the container engine caught foundry pioneered the idea of service brokers, something that we're all working on together in the open service broker API project and is in the process of incorporating technology.

A

It's like sto and envoy into the design of the cloud foundry system with new projects like ireenie, were able to bring Cod foundry even closer to kubernetes and be able to leverage some of the underlying orchestration capabilities from kubernetes in the application stack that caught foundry provides I. Think what's missing for all of us is: are we all aligned around how we do build and how a developer can go from source code to a running system in a consistent way across these different environments?

A

If you'll get functions, the environments even more fragmented, every major cloud provider has their own function, stack that they've delivered as a service on their cloud platform, whether it's IBM HUD functions, lambda or functions on Google and Azure. If you look at the open source landscape, there's literally dozens of projects that are building service capabilities, some of those are aligned around kubernetes. Some of them aren't and that fragmentation I think holds us all back from being able to really leverage functions as part of the design of our applications.

A

Now, how do we move forward from this point? Yesterday, you heard about a project called K native and I. Think a native is an important catalyst for helping us start to work together on bringing functions and applications into our common cognitive stack in in a way that will allow us to really move forward and collaborate together around this common platform.

A

Kay native takes kubernetes and teaches it how to deal with build, how to deal with serving of applications and functions, and some of the unique requirements that we have in those Styles around startup, latency and scaling from nothing, and it allows us to have a common view of how events are passed into applications and defined in the system, and so I'm really excited about this journey that we're on to build a single unified platform for applications that supports general-purpose, container style, that supports functions and that supports applications so that developers can mix these technologies leverage the best of those technologies without edges and without friction as they mix and solve the problems for the next one years of applications.

A

Now in IBM, we really believe in this vision we're delivering these capabilities on our cloud and we're actually using these capabilities deeply in our cloud and I being proud. We have a kubernetes service called by Cass. Iks provides the foundation of kubernetes for our cloud, both our public and private cloud environments. Ips is, of course, built on kubernetes.

A

It's built on solid networking foundations like calico, it's built on container D and, on top of kubernetes, we've been able to run a vast diversity of workloads, we're running a foundry, we're running our Watson AI platform, so machine learning and deep learning on kubernetes we're running stateful databases and data warehouse systems, we're running consumer facing websites like whether comm we're running blockchain, we're partnering with our partners in the monitoring space like sis Digg and the logging space like vog DNA and we're running.

A

All of this diverse work load on a single platform and I think that's incredibly powerful, so I'm excited to help make this vision a reality. I invite you to work with us and everyone else in the community to make this real and help us build the platform for the next 20 years. Thank you.