Cloud Native Computing Foundation KubeCon + CloudNativeCon North America 2019 (San Diego), 22 Nov 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keynote: In Search of the Kubernetes "Rails" Moment - Bryan Liles

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: In Search of the Kubernetes "Rails" Moment - Bryan Liles, KubeCon + CloudNativeCon North America 2019 Co-Chair & Senior Staff Engineer, VMware

Back in 2005, David Heinemeier Hansson wowed the web programming world with his demonstration of creating a blog in 15 minutes. Rails' secret trick was convention over configuration or decreasing the decisions a developer has to initially make. Five years in, Kubernetes could benefit from a Rails moment. What could that moment look like, and what could it mean for developers who have to engage with Kubernetes? In this keynote, Bryan will explore what the landscape could look like with more developer-friendly tools and systems.

https://sched.co/UdQU

A

All right so yeah I'm gonna do a keynote, and so this is an interesting topic. I started on this idea months ago, and I said well. um This is probably gonna be on the last day of the conference. What could I say that would um really hurt the most amount of people, so my title today is called in search of the kubernetes rayless moment and in case this is not clear. I'm talking about Ruby on Rails. So who is this guy well I'm, introducing myself a lot today.

A

I am Bren Lyles senior staff engineer at VMware and I like alliteration, so celebrating the hip-hop culture, cars, computers and creating a better world. That is what I am about, but really I want to focus on this first item celebrating the hip-hop culture and what I'm going to present to you without actually even saying it is this talk, and this talk is hip-hop? Are you like what we're gonna do?

A

A top on hip-hop at a at a cloud native event, yeah we're gonna, do a talk on hip-hop and what I mean by hip-hop and what you probably think of it as hip-hop is um music. Like that song, that I was that I walked into multiple times that song is actually entitled hip, hop and the reason I chose that songs to craft. This particular message right now, hip hop is not just the music hip. Hop is DJ, hip hop is in, is basically emceeing, which I am doing right now.

A

Hip hop is graffiti, the graffiti art is hip-hop and hip-hop is b-boying, we'll get into that a little bit later and the reason I bring that up is I, think it will actually tie this together, but the first lyric of that song is when the music hits hits you in your brain.

A

You will feel no pain and I'm gonna tie that into kubernetes is that when we get our jobs right, when we actually figure out what we're doing our community will feel no pain, because we've fixed that our companies will feel no pain, because we were able to execute in a better fashion, so my whole life. This revolves around hip, hop and since I'm up on the stage I spent some time over the last year. Writing an application that is open.

A

Source I was like well, why not I talk about it for a second, so I am the project lead for this tool called Acton and the reason we created octant was because, when I talked to a developer and I say what is your problem with kubernetes and they're saying well, I, don't really know what's going on so the premise of octant was instead of asking our users to figure out figure out, what's going on? Why don't we just tell them believe it or not?

A

We know computers and we can tell people how to solve their problems so check out octant. It's pretty cool got a lot of great response from the project here and I'm. Just super happy to be able to share it so onto the talk and I'm from I. Forgive me for the flashing thing, but this right here this video is the start of a moment.

A

This video came out in 2005 and it's the rails, oops video, so David Hannah, Mayer Hanson, who I refer to as DHH for the rest of this talk created this blog post using this brand-new web framework. He called called Ruby on Rails in this video and the best part about this. Video was every 30 seconds. He would go oops oops oops, but at the end of it he had a fully functioning, albeit poorly styled web application that could serve as a blog.

A

In that moment, in 2005, going into 2006 actually changed how we think about writing software so with rails. We didn't really bring anything new to the table. It used this old esoteric, Japanese programming, language called Ruby, but what rails brought to the table was this idea of convention over configuration and that's what we're going to dive into in this talk?

A

So how does rails and kubernetes actually relate I, don't know and what lessons can kubernetes learn from rails so just to put it out there- and you know, pat ourselves, on the back according to github kubernetes is beating rails by watchers and stars and forks. So what really can this project that is actually way more popular than in Ruby on Rails learn from rails?

A

Well, let me go into this really interesting idea, like I'm a whole new thought here now, so I don't want to be I, don't want them to actually push anyone out, but this right here is Djamel. We love yamo right err, kidding you're, just making dear saying that. Let me feel better, no one who really loves Djamel, but I wanted to show this piece of yamo here. So this is a deployment for installing nginx into your cluster kind of neat.

A

Well, let's actually pick this apart a little bit so on on a line there and I actually have a crossed out now. If we only did want one replica, why do we have to specify replicas, let's get rid of it? Well, what if we so here's something it really is I understand why it is in kubernetes, but there's duplication inside of the amyl, because we actually specify selectors and we specified the pop labels and I know the reason why we do this. But you know what let's get rid of that too.

A

You know why? Don't we just assume everything is port, 80 and they're. Definitely good reasons why not to assume everything is port 80, but since we're deleting things like that too, so is this convention over configuration into rails? Can we just introduce more conventions and know into into our deployment yeah mo to make it simpler? Well, we could, but maybe you want to live miss check. Is this thing actually going to run? What will add that and I want a readiness check? This thing is ready to serve traffic well, I.

A

Had that too want to access the volume, because we have config data that lives on a store somewhere. Well put that in there I want to access secrets, well we're putting things in their minds, we'll put something else in there too, and here is the greatest role in the kubernetes ecosystem right now, pod affinities and anti affinities. That's how you would do a pod affinity and answer affinity.

A

Well, add that in there too, and what we're seeing now is that just having the idea of conventions does that make anything simpler and just, and we really need to think about how can we embrace this concept of rails and the kubernetes well just stripping out features it's not going to work.

A

So here's something that isn't said. Often enough, I hear this a lot I see it on social media we're not using kubernetes because it's in complex well, let me share something with you: kubernetes runs on bare metal, it runs in VMs, it runs in other people's clouds. It runs on your Raspberry Pi kubernetes supports multiple types of container runtimes, multiple types of networking, runtimes, multiple types of storage, runtimes and guess what people are shipping this software today, kubernetes complexity is neccesary complexity.

A

So when someone says it's too hard, it's just because, frankly, they're selfish and they only think about their particular problem. We need to create problems that help others. So how do we capture the essence of rails without diluting the power of kubernetes? Because we don't want to do that? We don't want to be selfish, so um I just can't help, but talk about more yeah, Mille and just because I'm on stage here and I'm, giving the keynote I'm gonna redefine some terms um yeah most for computers, it's not for humans. Humans can read it.

A

That's cool, but Hamill. Oh yeah, Mille is for computers so because I'm up here, making things up since yeah Mille is for computers, we'll just consider yeah Mille as assembler, because that's not a problem is it and because I love taking analogies and metaphors too far, let's write some assembler.

A

This is 8088 assembler, not confused with 65 it's similar or missed a similar or or smart or similar, or anything like that. I got to make this fit on a slide. So we're gonna write a program, real, quick, we're going to take thirteen hex and we're gonna move it to our a it's register. We're gonna call interrupt in and then we're going to move a 8000 and I know. That's not how you say it, but I like saying 8000.

A

Instead of a zero zero zero and then what we're going to do is we're gonna, move a XDS and we're gonna move zero to a X and then we're going to move a x di and then we're going to move seven and to d/l and then we're going to do something. Even crazier is we're going to move the L into es column, D I. What have we done? Okay?

A

Well, really, we haven't done much. We put a pixel where we changed our screen resolution if we're running dost on up to 320 by 240 or nor the screen not descriptive, not helpful, but this is how we used to write software, I, started writing programming and see- and my second link and my second thing that I got the touch was TASM, so I actually thought. This is how we wrote computers. This is how I thought we computer, but it's not productive.

A

We've learned lessons since then, and we can actually do things at a higher. This is the same kind of code and it's Python for Windows, but what, if I'm running a Mac? This is not helpful. What, if I'm running on Linux this is not helpful, so why do I show that well, I show it because I'm just working at the level gamal isn't really what we want. We want to work at higher level, but what does that higher level look like.

A

So here's what I want to be and I know a lot of my friends out there have tried to do this. I don't want to write animal I want my app to say: hey computers, I'm coming get yourself ready, but really I mean that's what you all want to, but because it isn't happening, we're all employed and we're talking about this thing. But this is where we want to be. We want to solve bigger problems, and now I want to do something else. Introduce you to some other terms.

A

Llvm fun note about LLVM is when LLVM started. It was called the low level virtual machine right now. Do you know? Llvm stands for its LLVM they're like screw it? No one can get it right. So we'll just call it LLVM. It's like it's a fun note, but LLVM is interesting. What it is is this a system where you specify a front end, and then you have an optimizer that optimizes and then you have a back end that does back end stuff and generally that back end stuff.

A

Is you create machine level code so, depending on the platform x86 s-64 arm arm 64, mips z/architecture? It can do all that. So, what's on the front end, it's our programming languages besides go it's funny. We use go but go, doesn't use. Llvm I think it should use LOV M, but it doesn't. But it's a Google thing, so things like GCC things like Julia things like the Haskell LLVM compiler, they compile to this front end and and they produce all this on the back end.

A

How can we actually learn from this or actually before that I'm gonna tell you why we have LOV M some smart people realized that with L of what we were solving the problems again and again and again and not the same way and not well. So we would have this problem where we needed to have some optimizations or we wanted to have a interpreter, and we want it to be able to do some just-in-time work on it.

A

What we wanted to have output and I wanted to compile this thing and I wanted to have arm and x86 64 LLVM helped us solve that problem. Now, as a language developer, I don't need to think about that. I can just write. I can just write to this front end and the front end will help this. But what what can we learn from that and kubernetes land?

A

Well, we can take that front, end, optimizer and back end and then what we can do is we can change the words so our app and its front and its intentions on the front end.

A

You know question marks, are the optimizer and that's what we need to figure out and the back end is the kubernetes back in and before I was saying that kubernetes gamal was assembler, but maybe it's not a similar, maybe it's machine code and no one wants the right machine code or think about machine code. So how do we turn our app innocence and intentions into this machine code? Aka, yeah moe! That's what we need to figure out and this is a keynote and not a Tech Talk.

A

So guess what I'm not gonna tell you how to do it I'm telling you to think about how to do it, and then I also want to remind you of this. Kubernetes is a vehicle taking us to our destination and out the destination itself too many times we focus on kubernetes as a product. It is not a product, it is a fancy car. Is it electric car or a gasoline-powered car I, don't know, but it is a car.

A

So let's go back to this middle box in this middle box, I just throw out some things, I'm going to be nice if we could just figure out how to automatically do CI or automatically do CD, or even if you work in a regulated environment, how to automatically do auditing and a lot of you have never worked for a bank or a health company and don't understand about auditors. But auditors are the people who mean well but Wow?

A

Yes, oh gosh and I'm not here to talk bad about anybody but yeah, my friends who work in regulated environments now um and then it is back end, here's something else. We don't want our developers, thinking about generating Yammer I'm, applying security policies. They should just work. You know, security policies are applied them or network policies. You know what they are apply them um wiring up observability. You know our developers should be developing, and should they be conscious of all this?

A

Yes, yes, they should, but should we hold up development because they can't understand how to wire observability? No, we should not so um I'm trying to think about how to say this, not controversially, okay, think about this. We have a horizontal line and we have a vertical line. The horizontal line line of landscape is our landscape. It's our ecosystem, it's all the projects and all the technologies that we require to be able to do.

A

What we want to do in this vertical line going up is all the organizations it's the ciencia, platinum and diamond and gold members. It's the people who need to make money in this space. We cannot mess up the line. We have to keep the line straight.

A

If all of our companies, what we should be doing is figuring out how to inject, whatever, goodness that we are going to inject without breaking the ecosystem, and this is one of the things that I love and one of the things that we actually were very conscious about when we're actually putting together cubic on cloud native, con you'll notice that none of the speakers up here really sold their companies, that's because them selling the companies is for the booths, then providing enhancements is their business. We don't want to alive this.

A

We all want to push out those opinions here. We want the ecosystem to not be broken, because one company needs to make money. There is plenty of opportunity for corporations to provide optimizations to our ecosystem without breaking our community, so real conviction over configuration. What does it mean? It means that basically I'm gonna give you a good set of defaults because I know what's happening, and this is the only type of my slides by the way you can use them until you outgrow them, and you can change them, but you don't break everything else.

A

Something else we can learn from rails things we have should have good defaults rails is really good at defaults. Our defaults should be easy to override in our primary job. Oh. Second typo in these slides is to find those good defaults, I'm senior staff engineer at VMware. My job should be called default.

A

Senior staff default engineer, you're, a principal architect, you're the principal architect of defaults- think about that so other things that kubernetes can learn from rails, and this will be fun pay attention because you're going to be like whoa, where else people freed people from thinking about serving web requests which led to people rethinking about the Sinatra project.

A

This was this random Ruby project um that actually allowed us to have Heroku and when, with Heroku, they actually led to us free thinking about how we thought about pass, which gave us a concept of git push her oku master, which inspired Deus Labs. To imitate that concept. I mean you know: yadda yadda, yadda, helm,.

A

And I could do it again: ghh developed rails and textmate, which move developers max max to use text mates. Most of you all here using text mate right now is because of Ruby on Rails developer thought. It was a good idea, think about that, um and this led to the resurgence of the text editor, which Oldman ultimately gave us via Skoda, crazy, faint, DHH and rails, for that I can do it again.

A

Rails freed Mac users to think about other problems which led to the creation of homebrew homebrew, is written in Ruby that esoteric Japanese language, which is actually pretty amazing. Rails, has inspired a whole generation of developers to think outside of the box and funny thing enough rails. Ruby on Rails got me on this stage right now, because I met Dan and we actually just realized.

A

We were both at the same Ruby on Rails event in 2006, together rails got us here so kubernetes on kubernetes Ruby on Rails moment is just simply making a better kubernetes and Cooper Day arm brailles moment is making the ecosystem better, because kubernetes allows us to think about the more important things you know. All these things we think about in kubernetes are fine, but that's not the important piece so we've been here before Linux did this, which is crazy.

A

We're not the first Linux went through the same journey, so my call to action is: let's make kubernetes and able our Germany's, let's find rails kubernetes moment and just to make sure that I'm ending this one, hip-hop I used to be able to do that.

A