Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2018 (Copenhagen), 14 Nov 2015

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keynote: Container-Native Dev-and-ops Experience: It's Getting Easier, Fast. - Ralph Squillace

Description

Want to view more sessions and keep the conversations going? Join us for KubeCon + CloudNativeCon North America in Seattle, December 11 - 13, 2018 (http://bit.ly/KCCNCNA18) or in Shanghai, November 14-15 (http://bit.ly/kccncchina18)

Keynote: Container-Native Dev-and-ops Experience: It's Getting Easier, Fast. - Ralph Squillace, Principal PM – Azure Container Platform, Microsoft

The theme of Austin's KubeCon was that kubernetes is still too hard for developers. The Azure team has been working hard to improve the ease of container-native app development, using 100% open source technology. Come see how much has changed building applications for Kubernetes; things you can use anywhere Kubernetes is; anywhere you are.

About Ralph
Ralph Squillace is a Principal Program Manager for the open-source, container-native dev and ops Kubernetes tooling built by Azure. He oversees contributions to Helm, Draft, Brigade, VS Code Kubernetes extensions, and any random thing that makes building apps in containers easier, faster, and more secure.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.

A

I want to talk briefly about the fact that we're building a whole bunch of open-source kubernetes tools to do container native application development. So this is the short version which was in Austin kubernetes application. Development was a little bit hard and it still is. We enjoy digging deep into the system. The community is still building amazing features that we can use, but it's still hard to build applications, and so that's the thing we've been focusing on right. We've tried to build applications to create a container native development style.

A

We want you to start with code right. We want you to work and debug. Normally we want you to automate your world and we want you to let kubernetes do everything else for you, which is really the idea. It's the goal and we're gonna do something today.

A

Show you the experience about how that might be we're gonna get started, we're gonna, add some custom services show you the inner loop of remote debugging and development, we're gonna attach to the world and we're going to show you or at least start see, ICD butwhen, since I only have so much time, we'll see whether it completes before we're done. So that's what we're gonna do go ahead and switch the moniker cuz. We should be.

A

Oh, no, no, no, don't switch the monitor because I failed to plug it in or you can switch it and there's no question that the screen sharing monitor trick in let's come kick in, please experience is gonna, be there okay and then we're gonna go mirror because I should have done this first, let's see there, we go and displays single display and apply, and we all hope it works.

A

Let's see if it does.

A

Hey and I only blew I only blew a minute there, all right. So now we got a mouse, so I don't shake too much. Let's get this out of the way and you'll see that what we've got is we could start with draft create and draft up for any language which gets you up and running and bootstrap very quickly, but we don't want to do that here because it's pretty easy to do. It's a solved problem in many ways and more than just Draft does that what we have running here is the next step.

A

You've got a go, Lang application, it's a container and right now it just returns a string, and you can see that it's already debugging, and so we should be able to go over here. If I can get make. My mouse hit the fire Firefox and we should be able to go to B.

A

And it's thinking.

A

And, of course, this worked just a moment ago.

A

So if we go over here and that's remote, debug golang I'm gonna do the cycle, because why not terminate unexpectedly but notice we just hit f5. Now we got to do now. We have a different demo. You get to watch a build right, but we're envious code and all we've done is hit f5 and what we're gonna do is not only build the containers so we're going to debug into the artifact that we have right we're releasing the application already. So it's waiting for the pod to come up.

A

This pot is coming up in West, junior, western Europe and that's in Dublin, and so it should be up and I'm going to sit there and go no. No. This will work again.

A

Well, I go down here and in theory, I've got a dat one there and waiting for hosts and I'm in ok. So we just did it live right and you can see that we hit a dig Bob a debug point in our application, which is it's difficult to control here.

A

So I'm gonna go ahead and scroll up a little bit, but we hit a debug point and you can tell that because you can actually look at the debug here and you can see that I'm in and I have variables I'm now dragging around my debug icon. Let's go get rid of that, but I'm in and I have variables from here to Dublin right we're live into the container and if I hit f5 again I just fall through and we should be able to switch back.

A

Then we say: hi keep pukani you now, that's one service and you've gotten bootstraps you've been up and running your debug natively. The next one is to go to a second service and have this and given that we did it live we're going to have a node service and we're going to do this. We're not going to get to the CIC D and now we're going to do debugging it's building a completely separate service and that service knows how to talk to the first one.

A

So as soon as it pushes it releases, we finished draft up. It already is going to connect to the debugger we're caught we're debugging from one node into one go container and the new bug debugger is attached and so to do that. What we're gonna do is hit 8081 now notice. We first we've hit the node debugger we hit f5 and we've jumped from node to a second debug, and now we bounced into go.

A

We are now remote, debugging, two separate containers, and we can do this not just from my machine, but you can actually share with other developers and team debug or resume whatever you might want to use now, I'm out of time, but I was going to actually just push that straight into production and do a DCI CD with Brigade, and that would deploy that same application and we can rerun the front-end debugger into the live production stream, which uses a different chart. But I want to thank you for watching.

A

All of these tools are open-source, they all run against kubernetes and they all run against any cube. Config that you have. That means your could. Cluster can be running in Azure. In this case it is, but it could be mini cube. It could be any other cloud provider or bare-metal whatever you have it's all open source and we're trying to make it so that it works really well for application developers. So you want to see more, come out down to the booth and we'll be trying to rebreathe it all over again.

A

Ok, thank you very much.