 We did this in Boston about a week and a half ago, especially the section at the beginning where you wanna see features and roadmaps and stuff. If you wanna take a look at that, these slides will all get posted, but if you just search for Red Hat OpenShift 4 Release Update on YouTube, the video's out there. Mike Baird who runs Product Management and Clayton and Derek who run engineering or kind of core of engineering go through a lot of things. So if you didn't feel like you got enough this week or you don't get a chance to go by the booth, check out that video as well. So I'll wrap this up and I'll kinda keep this part sort of short. We started doing these events about three and a half years ago at one of the very first Cubecons. It was really, really at the time about the technology, kind of about the clouds. Is, how does Kubernetes work? What are the basics? Today I think you found that it was much more about kind of what people are actually doing with the use cases. So first and foremost, thank you for coming. This event continues to grow. It's grown quite a bit over the last couple of years. I gotta grab some numbers for what today look like. But it's been fantastic to see as many people be interested in OpenShift as we see the rest of the growing Kubernetes. So thank you all for sticking around, for staying for eight hours. I know this is a lot to take in. If you didn't get anything, if you don't get your question answered, please come by the booth. We'll be here all week. So please come by the booth as well. I think nowadays what we tend to talk about more and more and this may sometimes overtake some of the technical conversation is it's much more about what people are doing. So if you get a chance, take advantage of that all day. I know Diane's been talking about meet your peers. If you're seeing people from your industry doing interesting things, not from your industry doing interesting things, this has turned out to be a really, really good networking event as much as it's a technical event. What can we learn from it? The other thing I kind of highlight all the time is over the last three years, these are, I think most of them, I hope I didn't leave anybody out, the companies who have been brave enough to come up and tell their story. And I highlight this not because it's a lot of logos, which is always great, but because these are the companies that, if you look at this and you say they're in my industry, they're a competitor to me, these folks are all somewhere between a year to two years along in their journey. And we've had people who say, we're not sure if we're ready to make a cloud journey or do digital transformation or dev ops or whatever that change thing is, there are a lot of companies who not only are out there telling their story, they're hiring, but they're sort of setting the agenda for their industry. So something to kind of keep in mind in terms of what's kind of happening in production out there. So this is called road ahead. I get the question all the time, hey, you do strategy, what does the road ahead look like? In some cases, it is people that wanna move brownfield things. So we've had, you know, banks tell us they're going to move core banking into containers onto this. We've seen people lift and shift stuff. Volvo runs all of their web sphere, IBM web sphere stuff on this. That seems like kind of an unusual on the surface thing, but it allowed them to very quickly move to leveraging public cloud as well. So we do see a certain amount of brownfield get moved over to containers. We also see a certain amount of greenfield with a whole bunch of restrictions. So we wanna do 12 factor applications, but we also then have to do other stuff. So part of it is going to be sort of greenfields with certain kind of hard restrictions about what's going on. And then we also see some greenfield stuff where the future isn't completely understood. So you may have heard today about Knative or about Istio or some of the early stuff in operators and you go, that sounds really cool, but what's the roadmap for two years? And in some cases, this stuff will have a roadmap for two years, but it's only nine months old. So we see kind of a broad mix of all of those things. We try and showcase that to you through a lot of the customer example stories that people are doing it. In some cases with AI and ML, in other cases, it's mobile. The nice thing is Kubernetes is really good at dealing with a lot of different use cases. I throw this up there just as a, why have I been sitting here for eight hours thing? We had a very large customer, a large energy customer who spoke last week at Red Hat Summit, but it told us this a couple of weeks ago. They said, I came to your event two years ago. We didn't really know anything about OpenShift. We didn't really know a whole lot about Kubernetes. We just sat and took notes. And then we kind of walked around and listened and told stories. They got up on stage two weeks ago and talked about having 100 different development groups around the world out finding new energy sources. This is a Fortune, I don't know, five company. But these events are really good for finding people that are doing things that you may not be sure that you're capable of doing. And then a couple of years later, 18 months later, 12 months later, we're seeing some pretty interesting results. So hopefully as you're sitting there and your butts sort of soar, the results of these things will kind of come back as you go back and take your notes. So on to the technology stuff. So I tend to look at this as, I think we're moving into about the third era of Kubernetes, which sounds crazy because there's really only been about six or seven or eight cube cons. It's only been around for about five years. But we've seen these very distinct leaps. The first sort of big thing was it went from a Google project to it had to be a well-governed open source project to getting some of the enterprises going, hey, that stuff sounds like a problem that I have, right? I'll give an example. We had a bank who was telling us this story. They moved from sort of web banking to mobile banking. And as far as consumer banking goes, there's really only one day that matters and that's Friday when we all get paid. And what they found was when it used to be on web banking, people would on average log in about one time a day because they'd log in from their office and they weren't really sure if people were looking. When it moved to mobile banking and it became their own personal device, people were logging in eight to 10 times a day because they really wanted to make sure they're getting paid. So for one day a week, 20% of the time, you have an 8x spike in what you do and people started going, that sounds like a web scale problem. Google's gonna give me the free software to do that, cool. The next generation became, well, I wanna do more stuff on that and we started seeing stateful sets and we started seeing batch jobs and we started seeing stateless and we started seeing other types of use cases which is kind of what you've seen from customers today. And then what we're moving into is really this third generation where it's how do I automate those things much more? How do I make the platform simpler to run? How do I run them across all sorts of different clouds? We've been talking about hybrid cloud and multi-cloud for four or five plus years. We're starting to see the rest of the industry go, yeah, that's a real thing even though maybe I run one public cloud. So I think we're really going to start to see this third generation be dominant in what's going on with KubeCon today but we will see it become things that are mainstream platform and product technologies over the next year or two. We built OpenShift for around about four or five years of feedback. Feedback from all of you. And the one big feedback that we got more than anything else was yes, Kubernetes is interesting and yes, containers are interesting and all those other things, blah, blah, blah. But what they ultimately, what you ultimately told us was we are going to run things on-prem in some cases. We're going to run things in the public cloud in some cases, but we want you to design the platform around is the ease of use, the simplicity, the things that we've come to expect from the public cloud experience. So while there were folks who were talked about being in banking and being in totally disconnected environments, they say, I want that simplicity. I want things to just run. I want them to run as a service. And so the big things that come out of OpenShift 4 that you'll see in 4.1 and then going forward is all about that, right? We want operations to be really simple. How many people were really used to doing three month upgrades for anything in infrastructure, right? I tell people all the time, if you were VMware admin, you did zero upgrades every three months. You did them every 12 to 18 months. If you were a Cisco admin, it was every 12 to 18 months. And then these crazy Kubernetes people come along and go, yeah, every three months, just CI, CD, that sucker, yellow baby, infrastructure. And people are like, you're out of your mind, dude. I run a bank. I run the federal government. I run military. I run defense. That stuff can't go down. No, no, no, every three months. We had to figure out how to find that right balance, right? We had to make sure that there was interoperability and standards. Everybody comes to us and says, yes, I like this, but in the future, we want to know that we could use something else. Cool, right? We want to know there's lots of stuff on demand. I don't want to just do databases. I want to do databases as a service. I want to do queuing as a service. I want to do Kafka as a service. We had to make sure those were all there. Obviously we talked about security. It is kind of funny to me that like 10, 15 years ago, everybody's parents were like, don't talk to strangers. And then us internet nerds were like, don't put your credit card on the internet. And now we just get on a phone and we get, we call strangers off the internet to come pick us up in a car and we just jump in their car. So, security's always sort of what it is. And then finally, we want to make sure there's broad application support. Rob talked about this about operators and you're going to hear about operators. I think he's got a keynote at some point this week talking about operators. Operators are very cool in the context of saying, I want things as a service. We want databases as a service. That's sort of the canonical example. This is kind of a good slide to help you go. What's the difference between, I deployed something, this is what the cloud-like experience looks like and this is what we could actually deliver as a service, right? So that's kind of cool. And then I got to thinking about it and I'm like, okay, all these folks are going to go home. They're going to go, hey, boss team, they said we should do operators and somebody's going to go, yeah, but what does it buy us? So I kind of did a little bit of math and this isn't totally right. It's not totally great, but it's a little bit. So I went out and I looked at like RDS, right? Kind of a canonical web or cloud thing. It costs you about $16,000 a year for a decent size one. So the one that costs about a buck 90 per. And then Amazon came along and said, you know, there's a lot of extra stuff that people always want with their databases as a service. They'd like it backed up. They'd like it highly available. They'd like it to sort of scale on demand and other stuff. So let's call that sort of the advanced RDS, right? They call it Aurora. The premium for Aurora is about $3,500 a year per database. And this isn't intended to be any sort of commentary on pricing for Amazon databases. But when you're talking about saying like, why would we think about doing databases? Essentially for $3,500 a year, you get, well, the cloud's charged you $3,500 a year to now do what we're essentially doing in operators included with the platform. And oh, by the way, this will be for the same operations in every single cloud environment. So that same operator that you wanna run on OpenShift in your cloud, on Prem, on Azure, on AWS, on anywhere, exactly the same. And the other thing is all of those databases that you typically get in the cloud are gonna be open source only. As you saw from the list that Rob showed and some other people showed, this is going to be both the open source ones as well as the commercial ones. So if you're like, hey, we want SQL, but we want Microsoft SQL, or we want Kafka, but we want Confluent Kafka, you can kind of go either path, right? So these slides will get published and so forth. These are just some of the ones that are out there. But kind of wanted to give you some numbers to talk about, yes, what does all this stuff mean? What does it mean in terms of dollars and cents? It's 3,500 bucks, 4,000 bucks, whatever your sort of thing is, but that just becomes an embedded feature. Now multiply that by however many databases you run, however many Kafka queues you run and so forth. So the other thing that comes up all the time and people ask us, so we had a bunch of questions about what's roadmap and what's things. There's an interesting thing that happens at this event that doesn't necessarily happen like at Red Hat Summit. So this week you will hear a whole bunch of new stuff get talked about. Something new will come out, it'll have a crazy weird name and it will be 0.0.01. And then everybody will go, dude, are you running that? Are you running that? Are you running the thing yet? And you'll be like, man, I'm not running the thing. Shit. Let's put some things in perspective. So Prometheus, which is very, very cool, took 18 months to get from version one to version two. Istio, which still evolving, still pretty cool, took 15 months to get from alpha to 1.0. Lots of people working on that. Knative has now taken nine months to get four sub-releases to not even sort of even GA. So as you're thinking about the cool stuff that comes out this week, it's always neat to have that squirrel moment, but it's taken the community a while to get there. So as you're thinking like, well, when am I gonna get this and when does it sort of become production or when is it gonna be ready for me? Cool thing is it's open source. You can go play with it right now. But the other thing is is you're setting expectations, set them appropriately for when this thing will get to the point where your business will run it in production or run it in something that you wanna go, move into something that you don't wanna support every single day, okay? The other thing I throw out all the time is there's always this perspective in the Kubernetes community that we're always on the latest and greatest, right? So let's see, it's May. So next month 1.15 will likely come out or July 1.15 will come out. And I always ask this question. How many of you are running 1.14 today? One guy in the back, he should get a trophy too. Okay, give him a thing. You have to take him home because Diane doesn't wanna take the box home either. So you're definitely getting an award. But here's the thing, how many of you know that most of the major cloud providers aren't running more than 1.12 at the latest? Amazon's running 1.12 now, Google actually skipped 1.12 because they had some struggles with it and they're still on 1.11, we're gonna be on 1.13. Essentially, and we sort of track this just so we know how well we're doing or not well doing, most everybody in the industry who makes this into something that becomes a product takes a little while to stabilize the thing. And I don't show this to sort of highlight one vendor versus the other, I also sort of show this for those of you that go, no, no, no, no, forget all that, we're doing it on our own. Okay, this is sort of the baseline for people that have world-class sets of teams. If you're rolling it faster than this, you're awesome, make sure you get a whole bunch of the badges out there. But if you're trying to figure out how reasonably would we take to get the newest stuff, it's not unusual to take four months or five months or six months. Because remember we said, all that other stuff that you were used to rolling out every 18 months or something, we're now asking you to roll out every three, four, five, six months. And all this stuff is public data, you kinda have to scrub through to people's websites, but it's all out there. So, trying to set some expectations as far as what it means to get from upstream stuff, cool, shiny stuff at an event like this, to something that you're going to use for whatever you do to actually make money, okay? So, with that in terms of where this stuff's going, so we tried to make the platform way better, one of the things that you'll see at this event is the focus of the event is still called KubeCon, but it's also CloudNativeCon. And we're seeing more and more of the things as Kubernetes becomes much more stabilized. We're trying to keep that core very small. We see some extensions to the APIs and so forth, but we're trying to avoid Kubernetes becoming that big tent, and we're seeing more and more of the projects that are interesting. All those ones I showed you are sort of outside of Kubernetes, right? Prometheus isn't part of Kubernetes, but it's great at monitoring Kubernetes. KNative isn't part of Kubernetes, but it's great at delivering function level applications on top of containers and Kubernetes. So, as you're looking at this week and you're starting to look at keynotes and you're looking at projects and you're like, how come they're all not just Kubernetes, whatever, it's because the design of what's going on is moving kind of around it and it's allowing the projects to be somewhat independent. Obviously they work together with the core, but they're somewhat independent. They're allowing that speed and flexibility and timing to sort of work itself out, okay? So, a couple of last things before you go. As far as learning, if you are a hands-on learner, I highly recommend learn.openshift.com. So, totally free. You log in with a browser. It's not scripted, but it's essentially like courseware where you're doing hands-on stuff, right? We work with a company called Catacoda that does these simulations for us. So, really good stuff if you wanna play around with basics of OpenShift, you wanna play with new stuff, you wanna play with Istio, you wanna play with KNative, great for hands-on. If you're kind of a visual kind of learner, Diane runs a great set of events, typically every week, probably not this week, but typically every week, with somebody from the community. Sometimes it's engineering, sometimes it's our technology partners. These are all out on YouTube. So, if you go and look up OpenShift Commons briefings, if you're an audio sort of learner, I run a podcast called PodCTL that typically is about once every week. Sometimes it's late. And it's a mix of Kubernetes stuff and OpenShift stuff. If you wanna go play with it, go to try.openshift.com. If we haven't mentioned that yet this week. And then if you're a reader or you wanna annoy your spouse on a vacation or something, all of these books are generally free. You can get them either from O'Reilly or Manning. Really good set for developer interaction, operations interaction, bunch of folks who live and breed this stuff every day. And then finally, if you haven't heard from Diane already, and by the way, give her a huge round of applause. These are really hard events to put on. If you get a chance and you want more of this or you want more chances to interact with stuff, we ask for one basic thing. We ask you to sign up. So if you go to commons.openshift.com and right there, kind of at the top, you can do it. There's a bunch of cool stuff. The cool stuff being you're gonna learn things. You're gonna learn from other smart people. You have access to being on Diane's mailing list for learning about the weekly things that are going on. It's free. Go do it now. It's still free if you haven't done it yet. It's real simple. Who are you? And if you can sign up with your company, that's great as well. But we highly recommend that. So thank you all for being here all day. This has been great for us to get your feedback. We will be around some if you wanna ask questions. And if you don't get us, you're gonna go have a beer, go have dinner. Please come by the booth and come talk to us. So thank you very much.