>>The cube presents, Coon and cloud native con Europe, 22 brought to you by the cloud native computing foundation. >>Welcome to ity of Spain and cube con coup con cloud native con Europe 2022 is near the end of the day. That's okay. We, we, we have plenty of energy because we're bringing it. I'm Keith Townsend, along with my coho, Paul Gillon Paul, this has been an amazing day. Thus far. We've talked to some incredible folks. You got a chance to walk the show floor. Yeah. So I'm really excited to hear what's the vibe of the show floor, 7,500 people in Europe following the protocols, but getting stuff done. >>Well, first I have to say that I haven't traveled for two years. So getting out to a show by, by itself is, is an amazing experience, but a show like this with all of the energy and the crowd, she is enormously crowded at lunchtime today. It's hard to believe how many people have made it, made it all the way here out on the floor. The boots are crowded. The, the demonstrations are what you would expect at a show like this. Lots of code, lots of, lots of block diagrams, lots of architecture. I think the audience is eating it up. You know, when they're, they're on their laptops, they're coding on their laptops. And this is very much symbolic of the crowd that comes to a cubic con. And it's, it's a, just a delight to see them outta here. I so much fun. >>So speaking of lots of gold, we have Bome Toro co-founder of pet trade, but, you know, just saw, didn't realize this Isto becoming part of CNCF was the latest on infield. >>Yeah. Is still is, you know, it was always one of those service mesh projects, which was very widely adopted. And it's great to see that going into the cloud native computing foundation. And I think what happened with Kubernetes, like just became the defacto container orchestrator. I think similar thing is happening with Isto and service mesh. >>What, >>So I'm sorry, Keith, what's the process like of becoming adopted by and incubated by the CNCF? >>Yeah, I mean, it's pretty simple. It's an application process into the foundation where you say, you know what the project is about, how diverse is your contributor base, how many people are using it. And it goes through a review of with TC. It goes through a review of like all the users and contributors. And if you see a good base of deployments in production, if you see a diverse of contributors, then you can basically be part of the CNCF. And as you know, CNCF is very flexible on governance. Basically it's like, bring your own governance. And then the projects can basically seamlessly go in and, you know, get into incubation and gradually graduate >>Another project close and dear to you Envoy. Yes. Now I've always considered Envoy just as what it is. It's a, I've always used it as, as a load balancer type thing. So I've always considered it somewhat of a gateway proxy, but Envoy gateway was announced last week. Yes. >>So Envoy is basically won the data plane war of in cloud native workloads. Right. And, but, and this was over the last five years, Envoy was announced even way before Rio and it is used in various deployment models. You can use it as a front load balancer. You can use it as an Ingres in Kubernetes. You can use it as a side car and a service mesh like steel, and it's lightweight dynamically, programmable, very open with a white community. But what we looked at when we looked at the Envoy base, was it still, wasn't very approachable for application developers. Like when you still see like the nouns that it uses in terms of clusters and so on is not what an application developer was used to. And so Envoy gateway is really an effort to make Envoy even more stronger out of the box for an application developer to use it as an API gateway. >>Right? Because if you think about it, ultimately, you know, people de developers start deploying workloads onto their Kubernetes clusters. They need some functionality like an API gateway to expose their services and you wanna make it really, really easy and simple. Right? I often say like what, what engine X was to like static websites like Envoy gateway will be to like, you know, APIs and it's really few the community coming together. We are a big part, but also VMware and as well as end users, like in this case, fidelity who is investing heavily into Envoy and API gateway use cases, joining forces saying, let's do this in upstream Envoy. >>I'd like to go back to IIO because this is a major step in IIOS development. Where do you see SIO coming into the picture? And Kubernetes is already broadly accepted. Is IIO generally adopted as an after an after step to, to Kubernetes or are they increasingly being adopted together? >>Yeah. So usually it's adopted as a follow on step and the reason is primarily the learning curve, right. It's just get used to all the Kubernetes and, you know, it takes a while for people to understand the concepts, get applications going, and then, you know, studio was made to basically solve, you know, three big problems there. Right. Which is around observability traffic management and security. Right. So as people deploy more services, they figure out, okay, how do I connect them? How do I secure all the connections and how do I do more fine grain routing? I'm doing more frequent deployments with Kubernetes, but I would like to do Canary releases to make safer rollouts. Right. And those are the problems that Isto solves. And I don't really want to know the metrics of like, yes, it'll be, I it's good to know all the node level and CPO level metrics. >>But really what I want to know is how are my services performing? Where is the latency, right? Where is the error rate? And those are the things thatto gives out of the box. So that's like a very natural next step for people using Kubernetes. And, you know, Tetra was really formed as a company to enable enterprises, to adopt STO Envoy and service mission, their environment. Right? So we do everything from run an academy for like courses and certifications on Envoy and STO to a distribution, which is, you know, compliant with various bills and tooling as well as a whole platform on top of STO to make it usable and deployment in a large enterprise. >>So paint the end to end for me, for STO in Envoy. I know they can be used in similar fashions is like side cars, but how they work together to deliver value. >>Yeah. So if you step back from technology a little bit, right, and you like, sort of look at what customers are doing and facing, right. Really it is about, they have applications. They have some applications that new workloads going into Kubernetes and cloud native. They have a lot of legacy workloads, a lot of workloads on VMs and with different teams in different clouds or due to acquisitions. They're very heterogeneous right now. Our mission Tetrad's mission is power. The world's application traffic, but really the business value that we are going after is consistency of application operations. Right? And I'll tell you how powerful that is because the more places you can deploy Envoy into the more places you can deploy studio into, the more consistency you can get for the value pillars of observability, traffic management, and security. Right. And really, if you think about what is the journey for an enterprise to migrate from workloads into Kubernetes or from data centers into cloud, the challenges are around security and connectivity, right? Because if it's Kubernetes fabric, the same Kubernetes app and data center can be deployed exactly as is it in cloud. Right. Right. So why is it hard to migrate to cloud, right. The challenges come in the security and networking layer. >>Right. So let's talk about that with some granularity and you can maybe gimme some concrete examples, right? Because it, as I think about the hybrid infrastructure where I have VMs on premises, cloud, native stuff, running in the public cloud, or even cloud native next to VMs, right. I do security differently when I'm in the VM world. I say, you know what, this IP address, can't talk to this Oracle database server. Right. That's not how cloud native works. Right. I, I can't say if I have a cloud, if I have a cloud native app talking to a Oracle database, there's no IP address. Yeah. But how do I, how, how do I secure the communication between the two? Exactly. >>So I think you hit it straight on the head. So which is with things like Kubernetes, IP is no longer a really a valid noun where you can say, because things will auto scale either from Kubernetes or, you know, the cloud autoscales. So really the noun that is becoming now is service. So, and I could have many instances of it. They could go scale up and down. But what I'm saying is this service, which, you know, some app server, some application can talk to the article service. Hmm. And what we have done with the te trade service bridge, which is why we call our platform service bridge, because it's all about bridging all the services is whatever you're running on, the VM can be onboarded onto the mesh, like as if it were a ity service. Right. And then my policy around this service can talk to this service is same in Kubernetes is same for Kubernetes talking to VM it's same for VM to VM, both in terms of access control in terms of encryption. What we do is because it's the Envoy, proxy goes everywhere and the traffic is going through them. We actually take care of distributing, certs, encrypting, everything, and it becomes, and that is what leads to consistent application operations. And that's where the value is. >>We're seeing a lot of activity around observ observability right now, a lot of different tools, both open source and proprietary STO certainly part of the open telemetry project, I believe. Are you part of that? Yes. But the customers are still piecing together a lot of tools on their own. Right. Do you see a, a more coherent framework forming around observability? >>I think very much so. And there are layers of observability, right? So the thing is like, if we tell you there is latency between these two services at L seven layer, the first question is, is it the service? Is it the Envoy? Or is it the network? It sounds like a very simple question. It's actually not that easy to answer. And that is one of the questions we answer in like platforms like ours. Right. But even that is not the end. It, if it's neither of these three, it could be the node. It could be the hardware underneath. Right. And those, you realize like those are different observability tools that work on each layer. So I think there's a lot of work to be done, to enable end users to go from app, like from top to bottom to make, reduce what is called MTTR or meantime to, you know, resolution of an issue, where is the problem. >>But I think with tools like what is being built now, it is becoming easier, right? It is because one of the things we have to realize is with things like Kubernetes, we made the development of microservices easier. Right. And that's great. But as a result, what is happening is that more things are getting broken down. So there is more network in between. So that's harder. It gets to troubleshoot harder. It gets to secure everything harder. It gets to get visibility from everywhere. Right. So I often say like, actually, if you're going embarking down microservices journey, you actually are, you better have a platform like this. Otherwise, you know, you're, you're taking on operational cost. >>Wow. J's paradox. The more accessible we make something, the more it gets used, the more complex it is. That's been a theme here at KU con cloud native con Europe, 2022 from Licia Spain. I'm Keith Townsend, along with my host, Paul Gillman. And you're watching the queue, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe 22 brought to you by the cloud native computing foundation. >>Welcome to Licia Spain in Coon cloud native con Europe, 2022. I'm your host, Keith Townson, along with Paul Gillon senior editor, enterprise architecture for Silicon angle. Paul, we're gonna talk to some amazing people this week. Coon, what the energy here, what, what, what would you say about >>It? I'd say it's reminiscent of, of early year, early stage conferences I've seen with other technologies. There is a lot of startup activity. Here's a lot of money in the market, despite the selloff in the stock market lately, a lot of anticipation that there are, there could be big exits. There could be big things ahead for these companies. You don't see that when you go to the big established conferences, you see just anticipation here that I don't think you see you you'll see maybe in a couple of years. So it's fun to be here right now. I'm sure it'll be a very different experience in two or three years. >>So welcome to our guest Q alum. BAAM Tobar the founder and CEO of Upbound. Welcome back. >>Thank you. Yeah, pleasure to be on, on the show again. >>So Paul, tell us the we're in this phase of migrations and, and moving to cloud native stacks. Are we another re-platforming generation? I mean, we've done, the enterprise has done this, you know, time and time again, and whether it's from Java to.net or net to Java or from bare metal to VMs, but are we in another age of replatforming? >>You know, it's interesting. Every company has now become a tech company and every tech company needs to build a very model, you know, modern digital platform for them to actually run their business. And if they don't do that, then they'll probably be out of business. And it is interesting to think about how companies are platforming and replatforming. Like, you know, as you said, just a, a few years back, you know, we were on people using cloud Foundry or using Heroku, you hear Heroku a lot, or, you know, now it's cloud native and Kubernetes and, and it, it begs the question, you know, is this the end that the tr point is this, you know, do we have a, you know, what, what makes us sure that this is the, you know, the last platform or the future proof platform that, that people are building, >>There's never a last platform, right? There's always something around the core. The question is, is Kubernetes Linux, or is it windows? >>That, that's a good question. It's more like more like Linux. I think, you know, the, you know, you've heard this before, but people talk about Kubernetes as a platform off platforms, you can use it to build other platforms. And if you know what you're doing, you can probably put, assemble a set of pieces around it and arrive at something that looks and can work for your business. But it requires a ton of talent. It requires a lot of people that actually can act, you know, know how to put the stick together to, to work for your business. It is, there's not a lot of guidance. I, we were, I think we were chatting earlier about the CSCF landscape and, and how there all these different projects and companies around it. But, but they don't come together in meaningful ways that you have, they act the enterprise itself has to figure out how to bring them together. Right. And that's the combination of what they do there organically or not is their platform. Right. And that changes. It can change over time. >>Do you think they really do. They really want to put these things together? I mean, there's, that's not what enterprise is like to do. They want to find someone who's gonna come in and turnkey do it all for >>Them. Yeah. And, and if there were, this is the, this is the things like EV every week now you hear about another platform that says, this is the new Heroku. This is the new cloud Foundry. This replaces every, you know, some vendor has, and you can see them all around here. You know, companies that are basically selling platform solutions that do put 'em together. And the problem with it is that you typically outgrow these, like you are, it might solve 80% of the use cases you care about, but the other 20% are not represented. And so you end up outgrowing the platform itself, right? And the, the choice has been mostly around, you know, do you buy something off the shelf that solves 80% of your use cases? Or do you build something on your own? And then you have to spend all your resources actually going through and building all of it. And that's been the dilemma, you know, people who talk about this as a platform dilemma, but it's been, it's been the way for a long time. Like you, every, we go through this cycle every few years and, you know, people end up essentially oscillating between buying something off the, you know, that's off the shelf or building it, building it themselves. >>So what's the payoff. If I'm a CIO and I'm looking at the landscape, I don't need to understand, you know, I don't know what a pod is to know that looking at 200 plus projects in co and at, in cloud native foundation and the bevy of, of co-located projects and, and conferences before the, even the start of this, what's the payoff >>Increasing the pace of innovation. I mean, that literally is when we talk to customers, they all say roughly the same thing. They want something that works for their business. They want something that helps them take their, you know, line of business applications to production in a much quicker way, lets them innovate, lets them create higher engineers that can, don't have to understand everything about every system, but can actually specialize and focus on the, the parts that they sh they care about. But it's all in the context of, you know, people want to be able to innovate at a very high pace. Otherwise they get disrupted. >>So I was at the, you know, my favorite part of coan in general is the hallway track and talking to people on the ground, doing cool things. I was talking to a engineer who was able to take their Java, stack their, their.net stack and start to create APIs between and break 'em into microservices. Now teams are working across from one another realizing that, that, that promise of innovation, but that was the end point. They they're there. Yeah. As companies are thinking about replatforming where like, where do we start? I mean, I'm looking at the, the C CNCF, the, the map and it's 200 plus projects. Where, where do I start? >>You typically today start with Kubernetes. And, and a lot of companies have now deployed Kubernetes to production as a container orchestrator, whether they're going through a vendor or not. But now you're seeing all the things around it, whether it's C I C D or GI ops that they're looking at, you know, or they're starting to build consoles around, you know, their, their platforms or looking at managing more than just containers. And that's a theme that, you know, we're seeing a lot now, people want, people want to actually bring this modern stack to manage, not just container workloads, but start looking at databases and cloud workloads and everything else that they're doing around it. Honestly, everybody's trying to do the same thing. They're trying to arrive at a single point of control, a single, you know, a platform that can do it all that they can centralize policies, centralized controls to compliance governance, cost controls, and then expose a self-service experience to the developers. Like they're all trying to build what we probably call an internal cloud platform. They don't know, they talk about it in different ways, but almost everyone is trying to build some internal platform that sits on top of, on premises. And on top of cloud, depending on their scenarios, >>You make an interesting point, which is that everyone here is to some extent trying to do the same thing. And there's fine points of granularity between now they're approaching it as you walk around this floor. Do you understand what all of these companies are doing? >>I'm not sure I understand all of them, but I, I do. I do recognize a lot of them. Yes. >>And in terms of your approach, you, you use the term control plane. What is distinctive about your approach? >>Very good question. So, you know, we, we end, Upbound take a, we we're trying to solve this problem as well. We're trying to help people build their own platforms, but let me, let me, you know, there's a lot to it. So let me actually step back and, and talk about the architecture of this. But if you were to look at any cloud platform, let's take the largest one. AWS, if you peek behind the scenes at AWS, you know, it's basically a set of independent services, EC two S three databases, et cetera, that are, you know, essentially working on different parts of, you know, like offer completely different pricing, different services, et cetera. They come together because they all integrate into a control plan. >>It's the thing that serves an API. It's the thing that gives it all a common feel. It's where you do access control. It's where you do billing metering, cost control policy, et cetera. Right? And so our realization was if the enterprises are platforming and replatforming, why shouldn't they build their platform in the same way that the cloud vendors build theirs? And so we started this project almost four years ago, now three and a half years called cross plain, which is a, essentially an open source control plane that can become the integration point for all services. And essentially gives you a universal control plane for cloud. >>So you mentioned the idea of if orchestrating or managing stuff other than containers, as I think about companies that built amazing platforms, enterprise companies, building amazing applications on AWS 10 years ago, and they're adopting the AWS control plane. And now I'm looking at Kubernetes is Kubernetes the way to multi-cloud to be able to control those discrete services in a AWS or Google cloud Azure or Oracle cloud, is that true? >>We kind have the tease it, the parts. So there are really two parts to Kubernetes and everybody thinks of Kubernetes as a container orchestration platform. Right? And you know, there is a sense that people say, if I was to run Kubernetes on everywhere and can build everything on top of containers, that I get some kind of portability across clouds, right. That I can put things in containers. And then they magically run, you know, in different environments. In reality, what we've seen is not everything fits in containers. It's not gonna be the world is not gonna look like containers on the bottom. Everything else is on top. Instead, what we're gonna see is essentially a set of services that people are using across the different vendors. So if you look at like, you could be at AWS shop primarily, but I bet you're using confluent or elastic or data breaks or snowflake or Mongo or other services. >>I bet you're using things that are on premises, right? And so when you look at that and you say to build my platform as an enterprise, I have to consume services from multiple vendors. Even if it's just one major cloud vendor, but I'm consuming services from others. How do I bring them together in meaningful ways so that I can, you know, build my platform on top of the collection of them and offer something that my developers can consume. And self-service on. That's not a, that's not just containers. What's interesting though, is if you look at Kubernetes and, you know, look inside it, Kubernetes built a control plane. That's actually quite useful and applicable outside of container scenarios. So this whole notion of CRDs and controllers, if you've heard that term, the ability, you know, like there are two parts to Kubernetes, there is a control plane, and then there's the container container workloads. >>And the control plane is generic. It could be used literally across, you know, you can use it to manage things that are completely outside of container workloads. And that's what we did with cross mind. We took the control plane of Kubernetes and then built bindings providers that connected to AWS, to Google, to Azure, to digital ocean, to all these different environments. So you can bring the way of managing, you know, the style of managing that Kubernetes invented to more than just containers. You can now manage cloud services, using the same approach that you are now using with Kubernetes and using the entire ecosystem of tooling around it. >>Enterprise has been under pressure to replatform for a long time. It was first go to Unix then to Linux and virtualize then to move to the cloud. Now, Kubernetes, do you think that this is the stack that enterprises can finally commit to? >>I think if you take the orientation of your deploying a control plane within your enterprise, that is extensible, that enables you to actually connect it to all the things that are under your domain, that that actually can be a Futureproof way of doing a platform. And, you know, if you look at the largest cloud platforms, AWS has been around for at least 15 years now, and they really haven't changed the architecture of AWS significantly. It's still a control plane, a set of control planes that are managing services. >>It's a legacy >>They've added a lot of services. They've have a ton of diversity. They've added so many different things, but the architecture is still a hub and spoke that they've built, right? And if the enterprise can take the same orientation, put a control plane, let it manage all the things that are, you know, about today, arrive at a single point of control, have a single point where you can enforce policy compliance, cost controls, et cetera, and then expose a self-service experience to your developers that actually can become future proof. >>So we've heard this promise before the cloud of clouds, basically, yes, the, the, to be able to manage everything, what we find is the devils in the details. The being able to say, you know, a load balancer issuing a, a command to, to deploy a load balancer in AWS is different than it is in Azure, which is different than it is in GCP. How do, how do enterprises know that we can talk to a single control plane to do that? I mean, that just seems extremely difficult to manage. >>Oh yeah. That the approach is not, you're not trying to create a lowest common denominator between clouds. That's a really, really hard problem. And in fact, you get relegated to just using this, you know, really shallow features of each, if you're, if you're gonna do that, like your, your example of load balancers, load balances look completely different between between cloud vendors, the approach that we kind of advocate for is that you shouldn't think of them as you shouldn't try to unify them in a way that makes them, you know, there's a, there's a global abstraction that says, oh, there's a load balancer. And it somehow magically works across the different cloud vendors. I think that's a really, really hard thing to say, to do as you pointed out. However, if you bring them all under a same control plane, as different as they are, you're able to now apply policies. You're able to set cost controls. You're able to expose a self-service experience on top of them, even, even if they are very different. And that's, that's something that I think is, you know, been hard to do in the past. >>So BAAM, we'll love to dig deeper into this in future segments. And I'm gonna take a look at the, the, the product and project and see where you folks land in this conversation from Valencia Spain, I'm Keith towns, along with Paul Gillon and you're watching the leader in high tech coverage.

>>from around the >>globe it's the cube with >>coverage of Kublai >>Khan and Cloud Native Con Europe 2020 >>one virtual >>brought to you by red hat. The cloud native computing foundation and ecosystem partners. Welcome back to the cubes coverage of Kublai khan 21 cloud native gone 21 virtual. I'm john for your host of the cube. We're here with a great segment of an entrepreneur also the creator and maintainer of fluent bit Eduardo Silva who's now the founder of Palihapitiya was a startup. Going to commercialize and have an enterprise grade fluent D influence bit Eduardo. Great to have you on. Thanks for coming on the cube >>during the place for having me here. So I'm pretty happy to share the news about the crew and whenever you want, >>exciting trends, exciting trends happening with C N C f koo Kahne cloud native cloud native a lot of data, a lot of management, a lot of logging, a lot of observe ability, a lot of end user um contributions and enterprise adoption. So let's get into it first by give us a quick update on fluent D anything upcoming to highlight. >>Yeah, well fluent is actually turning two years old right now. So it's the more metric project that we have a lot of management and processing in the market. And we're really happy to see that the sides are project that was started 10 years ago, its adoption. You can see continues growing ecosystem from a planning perspective and companies adopting the technology that that is really great. So it's very overwhelming and actually really happy to take this project and continue working with companies, individuals and and right now what is the position where we are now with through And these are part of the Roma is like one of the things that people is facing not because of the tool because people have every time there has more data, more Metro services the system are scaling up is like about performance, right? And performance is critical if you're slowing down data processing actually you're not getting the data at the right time where you need it right. Nobody's people needs real time query is real time analysis. So from a security perspective we're going to focus a lot on everything that is about performance I would say for this year and maybe the other one, I would say that we won't see many new futures around fluently itself as as a project so we'll be mostly about back texting and performance improvements. >>Yeah, I definitely want to dig in with you on the data and logging challenges around kubernetes especially with and to end workflows and there's the different environments that sits in the middle of. But first before we get there, just take a minute to explain for the folks um not that savvy with fluent bit. What is fluent bit real quick, explain what it is. >>Okay, so I will start with a quick story about this, so when we started flowing the, we envision that at some point I'm talking about six years ago, right, all this IOT train or embedded or h will be available and for that you we got back to heavy right? If you have a constraint environment or you want to process data in a more faster way without all the capabilities at that time we say that he might not be suitable for that. So the thing is okay and it was not longer like a single software piece right? We want to say through in this an ecosystem, right? And as part of the ecosystem we have sck where people can connect applications fluid the but also we say we need like a flu Indie but that could be lightweight and faster. Burundi is reading ruby right? And the critical part in C. But since it's written ruby of course there's some process calls on how do you process the data and how much you can scale? Right. So we said if you're going to dig into embedded or small constrained environment, let's write a similar solution. But in C language so we can optimize a memory, can optimize scenario and all this kind of um needs will be will will be effective, right? And we started to spread called fluent bed and through a bit it's like a nowadays like a lightweight version of Wendy, it has started for the Marilyn knows, but after a few years people from the cloud space, I'm talking about containers, kubernetes, they started to ask for more futures for flowing it because they wanted they have influence, but also they wanted to have flowing better than because of it was lively and nowadays we can see that what fluent established the market and true indeed, we're getting around $2 million dollars every single day. So nowadays the attraction of the break is incredible. And it's mostly used to um want to collect logs from the files from system be and for most of coordinated environment disabled, process all this information on a pen, meta data and solve all the problem of how do I collect my data? How do I make sure that the data has the right context meta data and I'm able to deliver this data. So a central place like a job provider or any kind of storage. >>That's great. And I love the fact that's written C, which kind of gives the, I'll say it more performance on the code. Less overhead, get deeper closer um and people No, no, see it's high performance, quick, quick stats. So how old is the project through a bit, What version are you on? >>Uh, a little bit. It's, I'm not sure it is turning six or seven this year, 96. It's been around >>for a while. >>Yeah, yeah. We just released this this week, one at 73 right. We have done more than 100 releases actually really settled two and it's pretty past sometimes we have releases every 23 weeks. So the operation, the club medical system is quite fast. People once and more future more fixes and they don't want to wait for a couple of months for the next release. They wanted to have the continue image right away to test it out and actually sends away as a project. We worked with most of providers like AWS Microsoft actor google cloud platform, the demon for this fixes and improvements are in a weekly basis. >>You guys got a lot of props, I was checking around on the internet, you guys are getting strong um, reviews on logging for kubernetes with the couple releases ago, you had higher performance improvements for google AWS logged in postgres equal and other environments. Um but the question that I'm getting and I'm hearing from folks is, you know, I have end to end workflows and they've been steady. They've been strong. But as more data comes in and more services are connecting to it from network protocols, two Other cloud services, the complexity of what was once a straight straightforward workflow and to end is impacted by this new data. How do you guys address that? How would you speak to that use case? >>Well, for for us data we have taken approaches. Data for us is agnostic on the way that it comes from but that it comes from and the format that comes from for for example, if you talk about the common uses case that we have now is like data come from different formats. Every single developer use the all looking format come from different channels, TCP file system or another services. So it is very, very different. How do we get this data? And that is a big challenge. Right? How do we take data from different sources, different format and you try to unify this internal and then if you're going to talk for example to less exert let's say you Jason you're going to talk to africa, they have their own binary protocol. So we are kind of the backbone that takes all the data transfer data and try to adapt to the destination expected payload from a technical perspective. Yeah, is really challenging. Is really challenging also that Nowadays, so two years ago people was finding processing, I don't know 500,000 messages per second, But nowadays they won 10, 20 40,000. So prime architecture perspective Yeah, there are many challenges and and I think that the teamwork from the maintaining this and with companies has provided a lot of value, a lot of value. And I think that the biggest proof here is that the adoption like adoption and big adoption, you have more banks reported more enhancement requests. All right. So if I get >>this right, you got different sources of data collection issues. If you look on the front end and then you got some secret sauce with bit fluent, I mean uh inside the kubernetes clusters um and then you deliver it to multiple services and databases and cloud services. That that right. Is that the key? The key value is that is that the key value proposition? Did I get that right with fluent bit? >>Mhm. Yeah, I would say most of the technical implementation when the of the value of the technical implementation, I would say that is towards being the vendor neutral. Right? So when you come, when you go to the market and you go to the talk to bank institution hospital form and if the company right, most of them are facing this concept of bender looking right, they use a Bender database but you have to get married. So they're tooling, right? And I'm not going to mention any inventor name. Right? Actually it's very fun. Well for example, the business model, this company that start with S and ends with swung right? For example is you pay as much money so you pay as much money compared to the data that you ingested. But the default tools in just the whole data. But in reality if you go to the enterprise they say yeah. I mean just in all my data into Splunk or X provider right? But from 100 that I'm interesting, which I'm paying for, I'm just using this service to query at least 20 of the data. So why I mean just in this 80 extra I didn't get it right. That's why I want to send and this is real use case there's this language is really good for where is analyzed the data But they said yeah, 80 of my data is just a five data. I will need it maybe in a couple of months just I want to send it to Amazon history or any kind of other a archive service. So users, the value that says is that I want to have a mentor neutral pipeline which me as a user, I went to this side work went to send data, went to send it and also I can come to my bills. Right? And I think that is the biggest value. So you can go to the market. They will find maybe other tools for logging or tools for Matrix because there's a ton of them. But I think that none of them can say we are gender neutral. Not all of them can offer this flexibility to the use, right? So from a technical language performance but from an end user is being the neutrality. >>Okay. So I have to ask you then here in the C n C F projects that are going on and the community around um um fluent bit, you have to have those kinds of enhancements integrations, for instance, for not only performance improvement, but extensive bility. So enterprises there, they want everything right. They make things very >>complicated. They're very >>complicated infrastructure. So if they want some policy they want to have data ingestion policies or take advantage of no vendor lock in, how is the community responding? How did what's your vision for helping companies now? You've got your new venture and you got the open source project, How does this evolve? How do you see this evolving eduardo? Because there is a need for use cases that don't need all the data, but you need all the data to get some of the data. Right. So it's a you have a new new >>paradigm of >>coding and you want to be dynamic and relevant. What's the how do you see this evolving? >>Yeah. Actually going to give you some spoilers. Right. So some years before report. Yeah. So users has this a lot of they have a lot of problems how to collect the data processing data and send the data. We just told them right, Performance is a continuous improvement, Right? Because you have always more data, more formats, that's fine. But one critical thing that people say, hey, you say, hey, I want to put my business logic in the pipeline. So think about this if you have to embed we are the platform for data. Right? But we also provide capabilities to do data processing because you can grab the data or you can do custom modifications over the data. One thing that we did like a year two years ago is we added this kind of stream processing capabilities, can you taste equal for Kaka? But we have our own sequel engine influence them. So when the data is flowing without having any data banks, any index or anything, we can do data aggregation. You can, you can put some business logic on it and says for all the data that matches this pattern, stand it to a different destination, otherwise send it to caracas plan or elastic. So we have, this is what we have now. Extreme processing capabilities. Now what is the spoiler and what we're going next. Right now there are two major areas. One of them is distributed. Extreme processing right? The capabilities to put this intelligence on the age, on the age I'm referring to for example, a cooper needs note right or constrained environment, right? Communities on the age is something that is going on. There are many companies using that approach but they want to put some intelligence and data processing where the data is being generated. Because there is one problem when you have more data and you want to create the data, you have to wait and to centralize all the data in the database for your service. And there's a legend see right, millions sometimes hours because data needs to be in Mexico. But what about it? To have 100 of notes, but each one is already right, influenced it. Why you don't run the queries there. That is one of the features that we have. And well now talking from the challenges from spoil perspectives, people says, okay, I love this pipeline. I noticed Lambert has a political architecture but the language see it's not my thing, right? I don't want to go and see. Nobody likes see that we are honest about that. And there are many mass words about security or not just nothing, which is true, right? It's really easy to mess up things and see. Right? So, and we said, okay, so now our next level, it's like we're going to provide this year the ability to write your own plug ins in Western webassembly. So with the web is simply interface. You can run your own pregnancy goal, rust or any kind of weapon sending support language and translate that implementation to native. Wasn't that fluent that will understand. So C as a language won't be with one being longer uploaded for you as a developer. As a company that wants to put more business logic into the bike. Well that is one of the things that are coming up and really we already have some docs but they're not ready to show. So maybe we can expect something for us at the end of this year. >>Great stuff by the way, from a c standpoint us, old timers like me used to program and see, and not a lot of C courses being taught, but if you do know see it's very valuable. But again, to your point, the developers are are focused on coding the apps, not so much the underlying. So I think that's that's key. I will like to ask you one final question of water before we wrap up, how do you deploy fluid bid? What's the is it is that you're putting it inside the cluster? Is there is that scripts, What's the what's the architecture real quick? Give us a quick overview of the architecture. >>Okay, so that it's not just for a classroom, you can run it on any machine. Windows, Linux, IBM Yeah, and that doesn't need to be a kubernetes. Classic. Right? When we created to invade Copernicus was quite new at the same time. So if you talk about kubernetes deploys as a demon set at the moment is pretty much a part that runs on every note like an agent. Right? Uh, all you can run necessarily on any kind of machine. Oh and one thing before we were, I just need to mention something that from the spoil it. But because it's just getting, we're having many news these days. Is that fluently used to be mostly for logging right? And influence the specifically project. We've got many people from years ago saying, you know what? I'm losing my agent for logging to a bed but I have my agents for metrics and sometimes this is quite heavy to have multiple agents on your age. So now flowing bed is extending the capabilities to deal with native metrics. Right. The first version will be available about this week in cuba come right. We will be able to process host matrix for application metrics and send them to permit use with open matrix format in a native way. So we extended the political system to be a better citizen with open metrics and in the future also with open telemetry, which is a hot thing that is coming up on this month. >>Everyone loves metrics. That's super important. Having the data Is really, really important as day two operations and get all this stuff is happening. I wanna thank you for coming on and sharing the update and congratulations on. The new venture will keep following you and look good for the big launch but fluent bit looking good. Congratulations. Thanks for coming on. >>Thank you so much help governments. >>Okay this is the cubes coverage of Kublai khan 21 cloud Native Con 21 virtual soon we'll be back in real life at the events extracting the signal from the noise. Thanks for watching. Yeah.

>>from around the globe. It's the Cube with coverage of Coop Con and Cloud, Native Con Europe 2020 Virtual brought to You by Red Hat, The Cloud Native Computing Foundation and its ecosystem Partners. Hi, I'm stupid, man. And this is the Cube's coverage of Cube con Cloud Native Con Europe event, which, of course, this year has gone virtual, really lets us be able to talk to those guests where they are around the globe. Really happy to welcome back to the program. Liz Rice. First of all, she is the vice president of Open Source Engineering at Aqua Security. She's also the chair of the Technical Oversight Committee has part of Ah CN cf. Liz, it is great to see you. Unfortunately, it's remote, but ah, great to catch up with you. Thanks for joining. >>Yeah, Thanks for having me. Nice to see you if you know across the ocean. >>So, uh, you know, one of the one of the big things? Of course, for the Cube Con show. It's the rallying point for the community. There are so many people participating. One of the things we always love to highlight its not only the the vendor ecosystem. But there is a very robust, engaged community of end users that participate in it. And as I mentioned, you're the chair of that technology oversight committee. So maybe just give our audience a little bit of, you know, in case they're not familiar with the TOC does. And let's talk about the latest pieces there. >>Yes, say the TOC is really hit. C can qualify the different projects that want to join the CNC F. So we're assessing whether or not they're cloud native. We're assessing whether they could joined at sandbox or incubation or graduation levels. Which of the different maturity levels that we have for for project within the CN CF yeah, we're really there, Teoh also provide it steering around the What does cloud native mean and what does it mean to be a project inside the CN CF community? We're also a voice for all of the projects. We're not the only voice, but, you know, part >>of our role >>really is to make sure the projects are getting what they need in order to be successful. So it's it's really around the technology and the projects that we call cloud native >>Yeah, and and obliges Cloud Native because when people first heard of the show, of course, Kubernetes and Cube Con was the big discussion point. But as you said, Cloud native, there's a lot of projects there. I just glanced at the sandbox page and I think there's over 30 in the sandbox category on and you know they move along their process until they're, you know, fully mature and reach that, you know, 1.0 state, which is the stamp of approval that, you know, this could be used in production. I understand there's been some updates for the sandbox process, so help us understand you know where that is and what's the new piece of that? >>Yeah. So it's really been because of the growth off cloud native in general, the popularity off the CN CF and so much innovation happening in our space. So there's been so many projects who want Teoh become hard off the CNC f family on and we used to have a sponsorship model where members of the TOC would essentially back projects that they wanted to see joining at the sandbox level. But we ran into a number of issues with that process on and also dealing with the scale, the number of applications that have come in. So we've revamped the process. We made it much easier for projects to apply as much simpler form where really not making so much judgment we're really saying is it's a cloud native project and we have some requirements in terms off some governance features that we need from a project. And it's worth mentioning that when a project joins the CN CF, they are donating the intellectual property and the trademark off that project into the foundation. So it's not something that people should take lightly. But we have tried to make it easier and therefore much smoother. We're able Teoh assess the applications much more quickly, which I think everyone, the community, the projects, those of us on the TOC We're all pretty happy that we can make that a much faster process. >>Yeah, I actually, it brings up An interesting point is so you know, I've got a little bit of background in standards committees. A swell as I've been involved in open source for a couple of decades now some people don't understand. You know, when you talk about bringing a project under a foundation. You talked about things like trademarks and the like. There are more than one foundation out there for CN CF Falls under the Linux Foundation. Google, of course, brought Kubernetes in fully to be supported. There's been some rumblings I've heard for the last couple of years about SDO and K Native and I know about a month before the show there was some changes along SDO and what Google was doing there may be without trying to pass too many judgments in getting into some of the political arguments, help us understand. You know what Google did and you know where that kind of comparison the projects that sit in the CN cf themselves. >>Yeah, So I e I guess two years ago around two years ago, Stu was very much the new kid in the cloud native block. So much excitement about the project. And it was actually when I was a program co chair that we had a lot of talks about sdo at Cube Con cloud native bomb, particularly in Copenhagen, I'm recalling. And, uh, I think everyone I just saw a natural fit between that project on the CN, CF and There was an assumption from a lot of people across the community that it would eventually become part of the CNC f. That was it's natural home. And one of the things that we saw in recent weeks was a very clear statement from IBM, who were one off the Uh huh, yeah, big contributing companies towards that project that that was also their expectation. They were very much under the impression that Stu would be donated to the CN CF at an appropriate point of maturity, and unfortunately, that didn't happen. From my point of view, I think that has sown a lot of confusion amongst the community because we've seen so much. It's very much a project of fits. Service mesh designed to work with kubernetes is it really does. You're fit naturally in with the other CN CF projects. So it's created confusion for end users who, many of whom assume that it was called the CN CF, and that it has the neutral governance that the other projects. It's part of the requirements that we have on those projects. They have to have an open governance that they're not controlled by a single vendor, Uh, and we've seen that you know that confusion, Andi. Frustration around that confusion being expressed by more and more end users as well as other people across the community. And yeah, the door is still open, you know, we would still love to see SDO join the community. Clearly there are different opinions within the SD wan maintainers. I will have to see what happens. >>Yeah, lets you bring up some really good points. You know, absolutely some of some of that confusion out there. Absolutely. I've heard from customers that if they're making a decision point, they might say, Hey, maybe I'm not going to go down that maybe choose something else because I'm concerned about that. Um, you know, I sdo front and center k native, another project currently under Google that has, you know, a number of other big vendors in the community that aiding in that So hopefully we will see some progress on that, you know, going forward. But, you know, back to you talked about, You know, the TOC doesn't make judgements as to you know which project and how they are. One of the really nice things out there in the CN CF, it's like the landscape just for you to help, understand? Okay, here's all of these projects. Here's the different categories they fit in. Here is where they are along that maturity. There's another tool that I read. Cheryl Hung blogged about the technology radar. I believe for continuous delivery is the first technology radar. Help us understand how that is, you know, not telling customers what to do but giving them a little guidance that you know where some of these projects projects fit. In a certain segment, >>Yeah, the technology radar is a really great initiative. I'm really excited about it because we have increasing numbers or end users who are using these different projects it both inside the CN CF and projects that are outside of the CNC F family. Your end users are building stacks. They're solving real problems in the real world and with the technology radar. What Cheryl's been able to facilitate is having the end you to the end user community share with us. What tools? They're actually using what they actually believe are the right hammers for specific nails. And, you know, it's it's one thing for us as it's more on the developer or vendor side Teoh look at different projects and say what we think are the better solutions for solving different problems. Actually hearing from the horse's mouth from the end users who are doing it in the real world is super valuable. And I think that is a really useful input to help us understand. What are the problems that the end user is still a challenge by what are the gaps that we still need to fail more input we can get from the end user community, the more will be solving real problems and no necessarily academic problems that we haven't sorry discovered in >>the real world. Alright, well is, you know, teeing up a discussion about challenges that users still have in the world. If we go to your primary jobs, Main hat is you live in the security world and you know, we know security is still something, you know, front and center. It is something that has never done lots of discussion about the shared responsibility model and how cloud native in security fit together and all that. So maybe I know there's some new projects there, but love to just give me a snap shot as where we are in the security space. As I said, Overall, it's been, you know, super important topic for years. This year, with a global pandemic going on, security seems to be raised even more. We've seen a couple of acquisitions in the space, of course. Aqua Security helping customers along their security journey. So what do you seeing out there in the marketplace today and hear from your custom? >>Yeah, I Every business this year has, you know, look at what's going on and you know, it's been crazy time for everyone, but we've been pleasantly surprised at how, you know, in relative terms, our business has been able to. It's been strong, you know. And I think you know what you're touching on the fact that people are working remotely. People are doing so many things online. Security is evermore online. Cloud security's evermore part off what people need to pay attention to. We're doing more and more business online. So, actually, for those of us in the security business, it has bean, you know that there have been some silver linings to this this pandemic cloud? Um, yes. So many times in technology. The open source projects and in particularly defaults in kubernetes. Things are improving its long Bina thing that I've you know, I wished for and talked about that. You know, some of the default settings has always been the most secure they could be. We've seen a lot of improvements over the last 23 years we're seeing continuing to see innovation in the open source world as well as you know, on the commercial side and products that vendors like Akwa, you know, we continue to innovate, continue to write you ways for customers to validate that the application workloads that they're going to run are going to run securely in the cloud. >>Alright and lives. There's a new project that I know. Ah, you know, you Aqua are participating in Tell us a little bit about Starbird. You know what's what's the problem? It's helping solve and you know where that budget >>Yes, So stockholders, one of our open source initiatives coming out of my team are equal on, and the idea is to take security reporting information and turn it into a kubernetes native, uh, resources custom resources. And then that means the security information, your current security status could be queried over the kubernetes AP I, as you're querying the status or the deployment, say you can also be clearing to see whether it's passing configuration audits or it's passing vulnerability scans for the application containers inside that deployment. So that information is available through the same AP eyes through the queue control interface through dashboards like Octane, which is a nice dashboard viewer for kubernetes. And starboard brings security information not just from acquittals but from other vendor tools as well front and center into that kubernetes experience. So I'm really excited about Star Border. It's gonna be a great way of getting security visibility, Teoh more kubernetes use it >>all right. And we were talking earlier about just the maturity of projects and how they get into the sandbox. Is is this still pretty sandbox for >>this? OK, we're still very much in the early phases and you know it. I think in the open source world, we have the ability to share what we're doing early so that we can get feedback. We can see how it resonates with with real users. We've had some great feedback from partners that we've worked with and some actual customers who actually collaborated with When we're going through the initial design, some great feedback. There's still lots of work to do. But, yeah, the initial feedback has been really positive. >>Yeah, is usually the event is one of those places where you can help try toe, recruit some other people that might have tools as well as educate customers about what's going on. So is that part of the call to action on this is, you know, what are you looking for for kind of the rest of 2020 when it when it comes to this project? >>Yeah, absolutely. So internally, we're working on an operator which will automate some of the work that's double does in the background in terms off getting more collaboration. We would love to see integrations from or security tooling. We're talking with some people across the community about the resource definition, so we've come up with some custom resource definitions, but we'd love them to be applicable it to a variety of different tools. So we want to get feedback on on those definitions of people are interested in collaborating on that absolutely do come and talk to me and my team are reluctant. >>Great. Listen, and I'll give you the final word. Obviously, we're getting the community together while we're part So you know any other you know, engagement opportunities, you get togethers. Things that you want people to know about the European show this year. >>Well, it's gonna be really you know, I'm on tenterhooks to see whether or not we can recreate the same atmosphere as we would have in Q con. I mean, it won't be exactly the same, but I really hope that people will engage online. Do come and, you know, ask questions of the speakers. Come and talk to the vendors, get into slack channels with the community. You know, this is an opportunity to pretend we're in the same room. Let's let's let's do what we can Teoh recreate as close as we can. That community experience that you keep corn is famous for >>Yeah, absolutely. That whole way track is something that is super challenging to recreate. And there's no way that I am getting the Indonesian food that I was so looking forward to in Amsterdam just such a great culinary and cultural city. So hopefully sometime in the future will be able to be back there. Liz Rice. Always pleasure catching up with you. Thanks so much for all the work you're doing on the TOC. And always a pleasure talking to you. >>Thanks for having me. >>All right, Lots more coverage from Cube Con Cloud, Native con the European 2020 show, Of course. Virtual I'm stew minimum. And thank you for watching the Cube. Yeah, yeah, yeah, yeah.

>>from around the globe. It's the Cube with coverage of Coop Con and Cloud, Native Con Europe 2020 Virtual brought to You by Red Hat, The Cloud Native Computing Foundation and its Ecosystem Partners. >>And welcome back to the Cube's coverage of Cube Con Cloud, Native Con Europe 20 twenties Virtual event. I'm Stew Minimum and and happy to Welcome back to the program, two of our Cube alumni. We're gonna be talking about storage in this kubernetes and container world. First of all, we have Sam Warner. He is the vice president of storage, offering management at IBM, and joining him is Brent Compton, senior director of storage and data architecture at Red Hat and Brent. Thank you for joining us, and we get to really dig in. It's the combined IBM and red hat activity in this space, of course, both companies very active in the space of the acquisition, and so we're excited to hear about what's going going. Ford. Sam. Maybe if we could start with you as the tee up, you know, Both Red Hat and IBM have had their conferences this year. We've heard quite a bit about how you know, Red Hat the solutions they've offered. The open source activity is really a foundational layer for much of what IBM is doing when it comes to storage, you know, What does that mean today? >>First of all, I'm really excited to be virtually at Cube Con this year, and I'm also really excited to be with my colleague Brent from Red Hat. This is, I think, the first time that IBM storage and Red Hat Storage have been able to get together and really articulate what we're doing to help our customers in the context of kubernetes and and also with open shift, the things we're doing there. So I think you'll find, ah, you know, as we talked today, that there's a lot of work we're doing to bring together the core capabilities of IBM storage that been helping enterprises with there core applications for years alongside, Ah, the incredible open source capabilities being developed, you know, by red Hat and how we can bring those together to help customers, uh, continue moving forward with their initiatives around kubernetes and rebuilding their applications to be develop once, deploy anywhere, which runs into quite a few challenges for storage. So, Brennan, I'm excited to talk about all the great things we're doing. Excited about getting to share it with everybody else. A cube con? >>Yes. So of course, containers When they first came out well, for stateless environments and we knew that, you know, we've seen this before. You know, those of us that live through that wave of virtualization, you kind of have a first generation solution. You know what application, What environment and be used. But if you know, as we've seen the huge explosion of containers and kubernetes, there's gonna be a maturation of the stack. Storage is a critical component of that. So maybe upfront if you could bring us up to speed you're steeped in, you know, a long history in this space. You know, the challenges that you're hearing from customers. Uhm And where are we today in 2020 for this? >>Thanks to do the most basic caps out there, I think are just traditional. I'm databases. APS that have databases like a post press, a longstanding APS out there that have databases like DB two so traditional APs that are moving towards a more agile environment. That's where we've seen in fact, our collaboration with IBM and particularly the DB two team. And that's where we've seen is they've gone to a micro services container based architecture we've seen pull from the market place. Say, you know, in addition to inventing new Cloud native APS, we want our tried true and tested perhaps I mean such as DB two, such as MQ. We want those to have the benefits of a red hat, open shift, agile environment. And that's where the collaboration between our group and Sam's group comes in together is providing the storage and data services for those state labs. >>Great, Sam, you know I IBM. You've been working with the storage administrator for a long time. What challenges are they facing when we go to the new architectures is it's still the same people it might There be a different part of the organization where you need to start in delivering these solutions. >>It's a really, really good question, and it's interesting cause I do spend a lot of time with storage administrators and the people who are operating the I T infrastructure. And what you'll find is that the decision maker isn't the i t operations or storage operations. People These decisions about implementing kubernetes and moving applications to these new environments are actually being driven by the business lines, which is, I guess, not so different from any other major technology shift. And the storage administrators now are struggling to keep up. So the business lines would like to accelerate development. They want to move to a developed, once deploy anywhere model, and so they start moving down the path of kubernetes. In order to do that, they start, you know, leveraging middleware components that are containerized and easy to deploy. And then they're turning to the I T infrastructure teams and asking them to be able to support it. And when you talk to the storage administrators, they're trying to figure out how to do some of the basic things that are absolutely core to what they do, which is protecting the data in the event of a disaster or some kind of a cyber attack, being able to recover the data, being able to keep the data safe, ensuring governance and privacy of the data. These things are difficult in any environment, but now you're moving to a completely new world and the storage administrators have ah tough challenge out of them. And I think that's where IBM and Red Hat can really come together with all of our experience and are very broad portfolio with incredibly enterprise hardened storage capabilities to help them move from their more traditional infrastructure to a kubernetes environment. >>Maybe if you could bring us up to date when we look back, it, like open stack of red hat, had a few projects from an open source standpoint to help bolster the open source or storage world in the container world. We saw some of those get boarded over. There's new projects. There's been a little bit of argument as to the various different ways to do storage. And of course, we know storage has never been a single solution. There's lots of different ways to do things, but, you know, where are we with the options out there? What's that? What's what's the recommendation from Red Hat and IBM as to how we should look at that? >>I wanna Bridget question to Sam's earlier comments about the challenges facing the storage admin. So if we start with the word agility, I mean, what is agility mean for it in the data world. We're conscious for agility from an application development standpoint. But if you use the term, of course, we've been used to the term Dev ops. But if we use the term data ops, what does that mean? What does that mean to you in the past? For decades, when a developer or someone deploying production wanted to create new storage or data, resource is typically typically filed a ticket and waited. So in the agile world of open shift in kubernetes, it's everything is self service and on demand or what? What kind of constraints and demands that place on the storage and data infrastructure. So now I'll come back to your questions. Do so yes. At the time, that red hat was, um, very heavily into open stack, Red Hat acquired SEF well acquired think tank and and a majority of the SEF developers who are most active in the community. And now so and that became the de facto software defying storage for open stack. But actually for the last time that we spoke at Coop Con and the Rook project has become very popular there in the CN CF as away effectively to make software defined storage systems like SEF. Simple so effectively. The power of SEF, made simple by rook inside of the open shift operator frame where people want that power that SEF brings. But they want the simplicity of self service on demand. And that's kind of the diffusion. The coming together of traditional software defined storage with agility in a kubernetes world. So rook SEF, open shift container storage. >>Wonderful. And I wonder if we could take that a little bit further. A lot of the discussion these days and I hear it every time I talk to IBM and Red Hat is customers air using hybrid clouds. So obviously that has to have an impact on storage. You know, moving data is not easy. There's a little bit of nuance there. So, you know, how do we go from what you were just talking about into a hybrid environ? >>I guess I'll take that one to start and Brent, please feel free to chime in on it. So, um, first of all, from an IBM perspective, you really have to start at a little bit higher level and at the middleware layer. So IBM is bringing together all of our capabilities everything from analytics and AI. So application, development and, uh, in all of our middleware on and packaging them up in something that we call cloud packs, which are pre built. Catalogs have containerized capabilities that can be easily deployed. Ah, in any open shift environment, which allows customers to build applications that could be deployed both on premises and then within public cloud. So in a hybrid multi cloud environment, of course, when you build that sort of environment, you need a storage and data layer, which allows you to move those applications around freely. And that's where the IBM storage suite for cloud packs was. And we've actually taken the core capabilities of the IBM storage software to find storage portfolio. Um, which give you everything you need for high performance block storage, scale out, um, file storage and object storage. And then we've combined that with the capabilities, uh, that we were just discussing from Red Hat, which including a CS on SEF, which allow you, ah, customer to create a common, agile and automated storage environment both on premises and the cloud giving consistent deployment and the ability to orchestrate the data to where it's needed >>I'll just add on to that. I mean that, as Sam noted and is probably most of you are aware. Hybrid Cloud is at the heart of the IBM acquisition of Red Hat with red hat open shift. The stated intent of red hat open shift is to be to become the default operating environment for the hybrid cloud, so effectively bring your own cloud wherever you run. So that that is at the very heart of the synergy between our companies and made manifest by the very large portfolios of software, which would be at which have been, um, moved to many of which to run in containers and embodied inside of IBM cloud packs. So IBM cloud packs backed by red hat open shift on wherever you're running on premises and in a public cloud. And no, with this storage suite for cloud packs that Sam referred to also having a deterministic experience. That's one of the things as we work, for instance, deeply with the IBM DB two team. One of the things that was critical for them, as they couldn't have they couldn't have their customers when they run on AWS have a completely different experience than when they ran on premises, say, on VM, where our on premises on bare metal critical to the DB two team t give their customers deterministic behavior wherever they can. >>Right? So, Sam, I I think any of our audience that it followed this space have heard Red House story about open shift in how it lives across multiple cloud environments. I'm not sure that everybody is familiar with how much of IBM storage solutions today are really this software driven. So ah, And therefore, you know, if I think about IBM, it's like, okay, and by storage or yes, it can live in the IBM Cloud. But from what I'm hearing from Brent in you and from what I know from previous discussion, this is independent and can live in multiple clouds, leveraging this underlying technology and can leverage the capabilities from those public cloud offers. That right, Sam? >>Yeah, that's right. And you know, we have the most comprehensive portfolio of software defined storage in the industry. Maybe to some, it's ah, it's a well kept secret, but those that use it No, the breadth of the portfolio. We have everything from the highest performing scale out file System Teoh Object store that can scale into the exabytes. We have our block storage as well, which runs within the public clouds and can extend back to your private cloud environment. When we talk to customers about deploying storage for hybrid multi cloud in a container environment, we give them a lot of houses to get there. We give them the ability to leverage their existing san infrastructure through the CS I drivers container storage interface. So our whole, uh, you know, physical on Prem infrastructure supports CS I today and then all the software that runs on our arrays also supports running on top of the public clouds, giving customers then the ability to extend that existing san infrastructure into a cloud environment. And now, with storage suite for cloud packs a sprint described earlier, we give you the ability to build a really agile infrastructure, leveraging the capabilities from Red Hat to give you a fully extensible environment and a common way of managing and deploying both on Prem and in the cloud. So we give you a journey with our portfolio to get from your existing infrastructure. Today, you don't have to throw it out it started with that and build out an environment that goes both on Prem and in the cloud. >>Yeah, Brent, I'm glad that you started with database, cause it's not something that I think most people would think about. You know, in a kubernetes environment, you Do you have any customer examples you might be able to give? Maybe Anonymous? Of course. Just talking about how those mission critical applications can fit into the new modern architect. The >>big banks. I mean, just full stop the big banks. But what I'd add to that So that's kind of frequently they start because applications based on structured data remain at the heart of a lot of enterprises. But I would say workload, category number two, our is all things machine Learning Analytics ai and we're seeing an explosion of adoption within the open shift. And, of course, cloud pack. IBM Cloud private for data, is a key market participant in that machine learning analytic space. So an explosion of the usage of of open shift for those types of workloads I was gonna touch just briefly on an example, going back to our kind of data data pipeline and how it started with databases, but it just it explodes. For instance, data pipeline automation, where you have data coming into your APS that are kubernetes based that our open shift based well, maybe we'll end up inside of Watson Studio inside of IBM ah, cloud pack for data. But along the way, there are a variety of transformations that need to occur. Let's say that you're a big bank. You need Teoh effectively as it comes in. You need to be able to run a CRC to ensure to a test that when when you modify the data, for instance, in a real time processing pipeline that when you pass it on to the next stage that you can guarantee well that you can attest that there's been no tampering of the data. So that's an illustration where it began, very with the basics of basic applications running with structured data with databases. Where we're seeing the state of the industry today is tremendous use of these kubernetes and open shift based architectures for machine learning. Analytics made more simple by data pay data pipeline automation through things like open shift container storage through things like open shift server lis or you have scale double functions and what not? So yeah, it began there. But boy, I tell you what. It's exploded since then. >>Yeah, great to hear not only traditional applications, but as you said so, so much interest. And the need for those new analytics use cases s so it's absolutely that's where it's going. Someone. One other piece of the storage story, of course, is not just that we have state full usage, but talk about data protection, if you could, on how you know things that I think of traditionally my backup restore and like, how does that fit into the whole discussion we've been having? >>You know, when you talk to customers, it's one of the biggest challenges they have honestly. And moving to containers is how do I get the same level of data protection that I use today? Ah, the environments are in many cases, more complex from a data and storage perspective. You want Teoh be able to take application consistent copies of your data that could be recovered quickly, Uh, and in some cases even reused. You can reuse the copies, for they have task for application migration. There's there's lots of or for actually AI or analytics. There's lots of use cases for the data, but a lot of the tools and AP eyes are still still very new in this space. IBM has made, uh, prior, uh, doing data protection for containers. Ah, top priority for our spectrum protect suite. And we provide the capabilities to do application aware snapshots of your storage environment so that a kubernetes developer can actually build in the resiliency they need. As they build applications in a storage administrator can get a pane of glass Ah, and visibility into all of the data and ensure that it's all being protected appropriately and provide things like S L A. So I think it's about, you know, the fact that the early days of communities tended to be stateless. Now that people are moving some of the more mission critical workloads, the data protection becomes just just critical as anything else you do in the environment. So the tools have to catch up. So that's a top priority of ours. And we provide a lot of those capabilities today and you'll see if you watch what we do with our spectrum. Protect suite will continue to provide the capabilities that our customers need to move their mission. Critical applications to a kubernetes environment. >>Alright And Brent? One other question. Looking forward a little bit. We've been talking for the last couple of years about how server lists can plug into this. Ah, higher kubernetes ecosystem. The K Native project is one that I, IBM and Red Hat has been involved with. So for open shift and server lis with I'm sure you're leveraging k native. What is the update? That >>the update is effectively adoption inside of a lot of cases like the big banks, but also other in the talk, uh, the largest companies in other industries as well. So if you take the words event driven architecture, many of them are coming to us with that's kind of top of mind of them is the need to say, you know, I need to ensure that when data first hits my environment, I can't wait. I can't wait for a scheduled batch job to come along and process that data and maybe run an inference. I mean, the classic cases you're ingesting a chest X ray, and you need to immediately run that against an inference model to determine if the patient has pneumonia or code 19 and then kick off another serverless function to anonymous data. Just send back in to retrain your model. So the need. And so you mentioned serverless. And of course, people say, Well, I could I could handle that just by really smart batch jobs, but kind of one of the other parts of server less that sometimes people forget but smart companies are aware of is that server lists is inherently scalable, so zero to end scalability. So as data is coming in, hitting your Kafka bus, hitting your object store, hitting your database and that if you picked up the the community project to be easy, Um, where something hits your relational database and I can automatically trigger an event onto the Kafka bus so that your entire our architecture becomes event >>driven. All right. Well, Sam, let me give you the funding. Let me let you have the final word. Excuse me on the IBM in this space and what you want them to have his takeaways from Cube con 2020 Europe. >>I'm actually gonna talk to I think, the storage administrators, if that's OK, because if you're not involved right now in the kubernetes projects that are happening within your enterprise, uh, they are happening and there will be new challenges. You've got a lot of investments you've made in your existing storage infrastructure. We had IBM and Red Hat can help you take advantage of the value of your existing infrastructure. Uh, the capabilities, the resiliency, the security of built into it with the years. And we can help you move forward into a hybrid, multi cloud environment built on containers. We've got the experience and the capabilities between Red Hat and IBM to help you be successful because it's still a lot of challenges there. But But our experience can help you implement that with the greatest success. Appreciate it. >>Alright, Sam and Brent, Thank you so much for joining. It's been excellent to be able to watch the maturation in this space of the last couple of years. >>Thank you. >>Alright, we'll be back with lots more coverage from Cube Con Cloud, native con Europe 2020 the virtual event. I'm stew Minimum And thank you for watching the Cube. Yeah, yeah, yeah, yeah

>>from around the globe. >>It's the Cube with >>coverage of Coop Khan and Cloud Native Con Europe 2020 Virtual brought to you by Red Hat Cloud, >>Native Computing Foundation and >>Ecosystem Partners. Hi. And welcome back. I'm stew Minuteman. And this is the cube coverage of que con cognitive con 2020. The Europe virtual addition Course kubernetes won the container wars as we went from managing a few containers that managing clusters, too many customers managing multiple clusters and that and get more complicated. So to help understand those challenges and how solutions are being put out to solve them, having a welcome back to the from one of our cube alumni do if it Gerald is the vice president and general manager of the management business unit at Red Hat. Joe, good to see you again. Thanks so much for joining us >>two. Thanks for having me back. >>All right, so at Red Hat Summit, one of the interesting conversation do you and I add, was talking about advanced cluster management or a CME course. That was some people and some technology that came over to Red hat from IBM post acquisition. So it was tech preview give us the update. What's the news? And, you know, just level set for the audience. You know what cluster management is? >>Sure, So advanced Cluster manager or a CMS, We actually falling, basically, is a way to manage multiple clusters. Ross, even different environments, right? As people have adopted communities and you know, we have at several 1000 customers running open shift on their starting to push it in some very, very big ways. And so what they run into is a stay scale. They need better ways to manage. It would make those environments, and a CMS is a huge way to help manage those environments. It was early availability back at Summit end of April, and in just a few months now it's generally available. We're super excited about that. >>Well, that that Congratulations on moving that from technical preview to general availability so fast. What can you tell us? How many customers have you had used this? What have you learned in talking to them about this solution? >>So, first of all, we're really pleasantly surprised by the amount of people that were interested in the tech preview. Integrity is not a product that's ready to use in production yet so a lot of times accounts are not interested in. They want to wait for the production version. We had over 100 customers in our tech review across. Not only geography is all over the world Asia, America, Europe, us across all different verticals. There's a tremendous amount of interest in it. I think that just shows you know, how applicable it is to these environments of people trying to manage. So tremendous had update. We got great feedback from that. And in just a few months, we incorporate that feedback into the now generally available product. So great uptick during the tech created >>Excellent Bring assigned side a little bit, you know, When would I use this solution? If I just have a single cluster, Does it make sense for May eyes? Is it only for multi clusters? You know, what's the applicability of the offering? Yes, sir, even for >>single clusters that the things that ACM really does fall into three major areas right allows closer lifecycle management. Of course, that would mean that you have more than one cluster ondas people grow. They do for a number of reasons. Also, policy based management the ability to enforced and fig policies and enforce compliance across even your single cluster to make sure that stays perfect in terms of settings and configuration and things like that. Any other application. Lifecycle management The ability to deploy applications in more advanced way, even if you're on a single cluster, gets even better for multi cluster. But you can deploy your APS to just the clusters that are tagged a certainly, but lots of capabilities, even for application, even a single cluster. So we find even people that are running a single cluster need it askew, deployed more more clusters. You're definitely >>that's great. Any you mentioned you had feedback from customers. What are the things that I guess would be the biggest pain points that this solves for them that they were struggling with in the past? Well, >>first of being able to sort of Federated Management multiple clusters, right, as opposed to having to manage each cluster individually, but the ability to do policy based configuration management to just express the way you want things to stay, have them stay that way to adopt a more of a getups ethnology in terms of how they're managing their your open ships environments. There's lots more feedback, but those were some of the ones that seem to be fairly common, repetitive across the country. >>Yeah, and you know, Joe, you've also gotten automation in the management suite. How do I think about this? How does this fit into the broader management automation that customers were using? Well, >>I think as people in employees environments. And it was a long conversation about platform right? But there's a lot of things that have to go with the platform and red hats actually in very good about that, in terms of providing all the things you necessary that you would find necessary to make the five form successful in your environment. Right? So I was seen by four. We need storage, then development environments management, the automation ability to train on it. We have our open innovation labs. There's lots of things that are beyond the platform that people acquire in order to be successful. In the case of management automation, ACM was a huge advancement. Terms had managed these environments, but we're not done. We're gonna continue to ADM or automation integration with things like answerable mawr, integration with observe ability and analytics so far from done. But we want to make sure that open ship stays the best managed environment that's out there. I also do want to make a call out to the fact that you know, this team has been working on this technology for the past couple of years. And so, you know, it's only been a red hat for five months. This technology is actually very mature, but it is quite an accomplishment for any company to take a new team in a new technology. And in five months, do what Red Hat does to it in terms of making it consumable for the enterprise. So then kudos continue. Really not >>well. And I know a piece of that is, you know, moving that along to be open source. So, you know, where are we with the solution? Now that is be a How does that fit in tow being open? Source. >>Eso supports that are open source Already. When the process of open sourcing the rest of it, as you've seen over time read, it has a perfect record here of acquiring technologies that were either completely closed Source Open core in some cases where part it was open. It was closed. But that was the case with Ansell a few years ago. But basically our strategy is everything has to be open source. That takes time in the process of going through all of the processes necessary to open source parts of ACM on. We think that will find lots of interest in the community around the different projects inside of >>Yeah. How about what? One of the bigger concerns talking to customers in general about kubernetes even Mawr in 2020 is. What about security? How does a CME help customers make sure that their environment to secure? >>Yeah, so you know, configuration policies and forcing you can actually sent with ACM that you want things to be a certain way that somebody changes them that automatically either warn you about them or enforcement would set them back. So it's got some very strong security chops in terms of keeping the configurations just the way you want. That gets harder as you get more and more clusters. Imagine trying to keep everything but the same levels, settings, software, all the parts and pieces so affected you have ACM that can do this across any and all of your clusters really took the burden off people trying to maintain secure environments, >>okay, and so generally available. Now, anything you can share about how this solution is priced, how it fits in tow. The broader open shift offerings, >>Yes. Oh, so it's an add on for open shift is priced very similarly to open shift in terms of the, you know, core pricing. One thing I do want to mention about ACM, which maybe doesn't come out just by a description product is the fact that a scene was built from scratch for communities, environments and optimize for open shift. We're seeing a lot of competition out there that's taking products that were built for other environments, trying to sort of been member coerce them into managing kubernetes environments. We don't think people are going to be successful at that. Haven't been successful to date. So one things that we find as sort of a competitive differentiator for ACM and market is the fact that it was built from scratch designed for communities environments. So it is really well designed for the environment it's trying to manage, and we think that's gonna keep your competitive edge? >>Well, always. Joe. When you have a new architecture, you advantage of things. Any examples that you have is what, what a new architecture like this can do that that an older architecture might struggle with or not believe. Be able to do even though when you look at the product sheet, the words sound similar. But when you get underneath the covers, it's just not a good architect well fit. >>Yeah, so it's very similar sort of the shift from physical to virtual. You can't have a paradigm shift in the infrastructure and not have a sort of a corresponding paradigm shift in management tool. So the way you monitor these environments, where you secure them the way they scale and expand, we do resource management, security. All those things are vastly different in this environment compared to, let's say, a virtual more physical environment. So this has improved many times in the past. You know, paradigm shift in the infrastructure or the application environment will drive a commensurate paradigm shift in management. That's what you're seeing here. So that's why we thought it was super important to have management that was built for these environments. by design. So it's not trying to do sort of unnatural things north manage the environment. >>Yeah, I wondered. I love to hear just a little bit your philosophy as to what's needed in this space. You know, I look back to previous generations, look at virtualization. You know, Microsoft did very well at managing their environment, the M where did the same for their environments. But, you know, we've had generations of times where solutions have tried to be management of everything, and that could be challenging. So, you know, what's Red Hat in a CM's position and what do we need in the community space, you know, today and for the next couple of years. >>So kubernetes itself is the automation platform you talked about, you know, early on in the second. So you know, Cooper navies itself provides, you know, a lot of automation around container management. What a CME does is build a top it out and then capture, you know, data and events and configuration items in the environment and then allows you to define policies. People want to move away from manual processes. Certainly, but they wanna be able to get to a more state full expression of the way things should be. You want to be able to use more about, you know, sort of get up, you know, kind of philosophy where they say, this is how I want things today. Check the version in, keep it at that level. If it changes, put it back. Tell me about it. But sort of the era of chasing. You know, management with people is changing. You're seeing a huge premium now on probation. So automation at all levels. And I think this is where a cm's automation on top of open shift automation on down the road, combined with things like ansell, will provide the most automated environment you can have for these container platforms. Um, so it's definitely changing your seeing observe ability, ai ops getups type of philosophies Coming in these air very different manager in the past helps you seeing innovation across the whole management landscape in the communities environment because they are so different. The physics of them are different than the previous environments. We think with ACM answerable or insights product and some over analytics that we've got the right thing for this environment >>and can give us a little bit of a look forward, you know? How often should we expect to see updates on this? Of course. You mentioned getting feedback from the community from the technical preview to G A. So give us a little bit. Look, you know, what should we be expecting to see from a CME down the right the So >>the ACM team is far from done, right? So they're going to continue to rev, you know, just like we read open shift, that very, very fast base we're gonna be reading ACM and fast face. Also, you see a lot of integration between ACM. A lot of the partners were already working with in the application monitoring space and the analytics space security automation I would expect to see in the uncivil fest time frame, which is mid October, will cease, um, integration with danceable on ACM around things. That insult does very well combined with what ACM does. A sand will continue to push out on Mawr cluster management, more policy based management and certainly advancing the application life cycles that people are very interested in ruined faster. They want to move faster with a higher degree of certainty in their application. Employments on ACM is right there. >>It just final question for you, Joe, is, you know, just in the broader space, looking at management in this kind of cube con cloud, native con ecosystem final words, you want customers to understand where we are today and where we need to go down the road. >>So I think the you know, the market and industry has decided communities is the platform of future right? And certainly we were one of the earliest to invest in container management platforms with open shift were one of the first to invest in communities. We have thousands of customers running open shift back Russell Industries on geography is so we bet on that a long time ago. Now we're betting on the management automation of those environments and bringing them to scale. And the other thing I think that redhead is unique on is that we think that people gonna want to run their kubernetes environments across all different kinds of environments, whether it's on premise visible in virtual multiple public clouds, where we have offerings as well as at the edge. Right. So this is gonna be an environment that's going to be very, very ubiquitous. Pervasive, deported scale. And so the management of a nation has become a necessity. And so but had investing in the right areas to make sure that enterprises continues communities particularly open shift in all the environments that they want at the scale. >>All right. Excellent. Well, Joe, I know we'll be catching up with you and your team for answerable fest. Ah, coming in the fall. Thanks so much for the update. Congratulations to you in the team on the rapid progression of ACM now being G A. >>Thanks to appreciate it, we'll see you soon. >>All right, Stay tuned for more coverage from que con club native con 2020 in Europe, the virtual addition on still minimum and thanks, as always, for watching the Cube.

>> live from Barcelona, Spain. It's the key covering Cook Con Cloud, Native Con Europe twenty nineteen by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners. >> Welcome back to the Cubes Live coverage of Cloud Native Con Cube Khan, twenty nineteen I'm student of my co host is Corey Quinn and happy to welcome back to the program. Doug Davis, who's a senior technical staff member and PM of a native and happens to be employed by IBM. Thanks so much for joining. Thanks for inviting me. Alright. So, Corey, I got really excited when he saw this Because server lists, uh, is something that, you know he's been doing for a while. I've been poking in, trying to understand all the pieces have done marvelous conflict couple of times and, you know, I guess, I guess layout for our audience a little bit, you know, Kay native. You know, I look at it kind of a bridging the solution, but, you know, we're talking. It's not the, you know, you know, containers or server. Listen, you know, we understand that world, they're spectrums, and there's overlap. So maybe is that is a set up. You know what is the service. Working groups, you know, Charter, Right. So >> the service Working Group is a Sand CF working group. It was originally started back in mid two thousand seventeen by the technical recite committee in Cincy. They basically wanted know what is service all about his new technology is that some of these get involved with stuff like that. So they started up the service working group and our main mission was just doing some investigation. And so the output of this working group was a white paper. Basically describing serval is how it compares with the other as is out there. What is the good use cases for when to use? It went out through it. Common architectures, basically just explaining what the heck is going on in that space. And then we also produced a landscape document basically laying out what's out there from a proprietors perspective as well is open source perspective. And then the third piece was at the tail end of the white paper set of recommendations for the TOC or seen staff in general. What should they do? Do next and basic came down to three different things. One was education. We want to be educate the community on what services, when it's appropriate >> stuff like that >> to what should wait. I'm sorry I'm getting somebody thinks my head recommendations. What other projects we pull into the CNC f others other service projects, you know, getting encouraged in the joint to grow the community. And, third, >> what should we >> do around improbability? Because obviously, when it comes to open source standards of stuff like that, we want in our ability portability, stuff like that. And one of the low hang your food so they identified was, Well, service seems to be all about events. So there's something inventing space we can do and we recognize well, if we could help the processing of events as it moves from Point A to point B, that might help people in terms of middleware in terms of routing, of events, filtering events, stuff like that. And so that's how these convents project that started. Right? And so that's where most of service working group members are nowadays. Is cloud events working or project, and they're basically divine, Eva said. Specification around cloud events, and you kind of think of it as defining metadata to add to your current events because we're not going to tell you. Oh, here's yet another one size fits all cloud of in format, right? It's Take your current events. Sprinkle a little extra metadata in there just to help routing. And that's really what it's all about. >> One of the first things people say about server list is quoted directly from the cover of Missing the Point magazine Server list Runs on servers. Wonderful. Thank you for your valuable contribution. Go away slightly less naive is, I think, an approach, and I've seen a couple of times so far at this conference. When talking to people that they think of it in terms of functions as a service of being able to take arbitrary code and run it. I have a wristwatch I can run arbitrary code on. That's not really the point. It's, I think you're right. It's talking more about the event model and what that unlocks As your application. Mohr less starts to become more self aware. Are you finding that acceptance of that point is taking time to take root? >> Yeah, I think what's interesting is when we first are looking. A serval is, I think, very a lot of people did think of service equals function of the service, and that's all it was. I think what we're finding now is this this mode or people are more open to the idea of sort of as you. I think you're alluding to merging of these worlds because we look at the functionality of service offers things like event base, which really only means is the messages coming in? It just happens to look like an event. Okay, fine. Mrs comes in you auto scale based upon, you know, loaded stuff like that scale down to zero is a one of the key. Thought it was really like all these other things are all these features. Why should you limit those two service? Why not a past platform? Why not? Container is a service. Why would you want those just for one little as column? And so my goal with things like a native though I'm glad you mentioned it is because I think Canada does try to span those, and I'm hoping it kind of merges them altogether and says, Look, I don't care what you call it. Use this piece of technology because it does what you need to do If you want to think of it as a pass. Go for I don't care. This guy over here he wants think that is a FAZ Great. It's the same piece of technology. Does the feature do what you need? Yes or no? Ignore that, nor the terminology around it more than anything else. >> So I agree. Ueda Good, Great discussion with the user earlier and he said from a developer standpoint, I actually don't want to think too much about which one of these pass I go down. I want to reduce the friction for them and make it easy. So you know, how does K native help us move towards that? You know, ideal >> world, right? And I think so fine. With what I said earlier, One of the things I think a native does, aside from trying to bridge all the various as columns is I also look a K native as a simplification of communities because as much as everybody here loves communities, it is kind of complicated, right? It is not the easiest thing in the world to use, and it kind of forced you to be a nightie expert which almost goes against the direction we were headed. When you think of Cloud Foundry stuff like that where it's like, Hey, you don't worry about this something, we're just give us your code, right? Cos well says, No, you gotta know about networks, Congress on values, that everything else it's like, I'm sorry, isn't this going the wrong way? Well, Kania tries to back up a little, say, give you all the features of Cooper Netease, but in a simplified platform or a P I experience that you can get similar Tokat. Foundry is Simo, doctor and stuff, but gives you all the benefits of communities. But the important thing is if for some reason you need to go around K native because it's a little too simplified or opinionated, you could still go around it to get to the complicated stuff. And it's not like you're leaving that a different world or you're entering a different world because it's the same infrastructure they could. This stuff that you deploy on K native can integrate very nicely with the stuff you deploy through vanilla communities if you have to. So it is really nice emerging these two worlds, and I'm I'm really excited by that. >> One thing that I found always strange about server list is a first. It was defined by what it's not and then quickly came to be defined almost by its constraints. If you take a look at public cloud offerings around this, most notably a ws land other there, many others it comes down well. You can only run it for experience, time or on Lee runs in certain run times, or it's something the cold starts become a problem. I think that taking a viewpoint from that perspective artificially hobbles what this might wind up on locking down the road just because these constraints move. And right now it might be a bit of a toy. I don't think it will be as it because it needs to become more capable. The big value proposition that I keep hearing around server listen I've mostly bought into has been that it's about business logic and solving the things that Air corps to your business and not even having to think about infrastructure. Where do you stand on that >> viewpoint? I completely agree. I think a lot of the limitations you see today are completely artificial I kind of understand why they're there, because the way things have progressed, But again, it's one reason I excited like a native is because a lot of those limitations aren't there. Now. Kay native doesn't have its own set of limitations. And personally, I do want to try to remove those. Like I said, I would love it if K native, aside from the service features it offers up, became these simplified incriminate his experience. So if you think about what you could do with Coronet is right, you can deploy a pod and they can run forever until the system decides to crash. For some reason, right, why not do that with a native and you can't stay with a native? Technically, I have demos that I've been running here where I set the men scale the one it lives forever, and teenager doesn't care right? And so deploying an application through K native communities. I don't care that it's the same thing to me. And so, yes, I do want to merge in those two worlds. I wantto lower those constraints as long as you keep it a simplified model and support the eighty to ninety percent of those use cases that it's actually meant to address. Leave the hard stuff for going around it a little. >> Alright, So, Doug, you know, it's often times, you know, we get caught in this bubble of arguing over, you know? You know what we call it, how the different pieces are. Yesterday you had a practitioner Summit four server list. So what? I want to hear his You know, whats the practitioners of you put What are they excited about? What are they using today and what are the things that they're asking for? Help it become, you know, Maur were usable and useful for them in the future. >> So in full disclosure, we actually kind of a quiet audience, so they weren't very vocal. But what little I did here is they seemed very excited by K native and I think a lot of it was because we were just talking about sort of the merging of the worlds because I do think there is still some confusion around, as you said, when to use one versus the other. And I think a native is helping to bring those together. And I did hear some excitement around that in terms of what people actually expect from us going the future. I don't know the honest They didn't actually say a whole lot there. I had my own personal opinion, and lot of is what already stayed in terms of emerging. Stop having me pick a technology or pick a terminology, right? Let me just pick technology gets my job done and hopefully that one will solve a lot of my needs. But for the most part, I think it was really more about Kenya than anything else yesterday. >> I think like Lennox before it. Any technology? At some point you saw this with virtual ization with cloud, with containers with Cooper Netease. And now we're starting to seriously with server lists where some of its most vocal proponents are also so the most obnoxious in that they're looking at this from a perspective of what's your problem? I'm not even going to listen to the answer. The solution is filling favorite technology here. So to that end today, what workloads air not appropriate for surveillance in your >> mind? Um, so this is hardly the answer because I have the IBM Army running through my head because what's interesting is. I do hear people talk about service is good for this and not this or you can date. It was good for this and not this. And I hear those things, and I'm not sure I actually buy it right. I actually think that the only limitations that I've seen in terms of what you should not run on time like he needed or any of the platform is whatever that platform actually finds you, too. So, for example, on eight of us, they may have time limited in terms of how long you can run. If that's a problem for you, don't use it to me. That's not an artifact of service. That's artifact of that particular choice of how the implement service with K native they don't have that problem. You could let it run forever if you want. So in terms of what workloads or good or bad, I honestly I don't have a good answer for that because I don't necessary by some of the the stories I'm hearing, I personally think, try to run everything you can through something like Cain native, and then when it fails, go someplace else is the same story had when containers first came around, they would say, You know when to use viens roses containers. My go to answer was, always try containers first. Your life would be a whole lot easier when it doesn't work, then look at the other things because I don't want to. I don't want to try to pigeonhole something like surly or K native and say, Oh, don't even think about it for these things because it may actually worked just fine for you, right? I don't want people to believe negative hype in a way that makes sense, >> and that's very fair. I tend to see most of the constraints around. This is being implementation details of specific providers and that that will dictate answers to that question. I don't want to sound like I'm coming after you, and that's very thoughtful of measured >> thank you Usual response back. Teo >> I'LL give you the tough one. The critical guy had in Seattle when I looked at K Native is there's a lot of civilised options out there yet, but when I talked to users, the number one out there is a ws lambda, and number two is probably as your functions and as of Seattle, neither of those was fully integrated since then. I talked a little startup called I Believe his Trigger Mash that that has made some connections between Lambda on K Native. And there was an announcement a couple of weeks ago, Kedia or Keita? That's azure and some kind of future to get Teo K native. So it feels like it's a maturity thing. And, you know, what can you tell us about, you know, the big cloud guys on Felicia? Google's involved IBM Red Hat on and you know Oracle are involved in K Native. So where do those big cloud players? Right? >> So from my perspective, what I think Kenya has going for it over the others is one A lot of other guys do run on Cooper Netease. I feel like they're sort of like communities as well as everything else, like some of them can run. Incriminate is Dr anything else, and so they're not necessary. Tightly integrated and leveraging the carbonates features the way Kay native is doing, and I think that's a little bit unique right there. But the other thing that I think K native has going for it is the community around it. I think people were doing were noticing. Is that what you said? There's a lot of other players out there and his heart feel the choose and what? I think Google did a great job of this sort of bringing the community together and said, Look, can we stop bickering and develop a sort of common infrastructure like communities is that we can all then base our surveillance platforms on, and I think that rallying cry to bring the community together across a common base is something a little bit unique for K native. When you compare it with the others, I think that's a big draw for people. Least from my perspective. I know it from IBM Zzzz Well, because community is a big thing for us, obviously. >> Okay, so will there be a bridge to those other cloud players soon as their road map? For that, >> we think a native itself. Yeah, I am not sure I can answer that one, because I'm not sure I heard a lot of of talk about bridging per se. I know that when you talk about things like getting events from other platforms and stuff, obviously, through the eventing side of a native. We do. But from a serving perspective, I'm not sure I hold her old water. From that perspective, you have to be >> honest. All right, Well, Doug Davis, we're done for This one really appreciate all the updates there. And I definitely look forward, Teo, seeing the progress that the servant working group continues to do, so thank you so much. Thank you for having me. Alright for Corey Quinn. I'm stupid and will be back with more coverage here on the Cube. Thanks for watching.

>> live from Barcelona, Spain. It's the key covering KubeCon Cloud, Native Con Europe twenty nineteen by Red Hat, the Cloud, Native Computing Foundation and Ecosystem Partners. >> Welcome back to Barcelona, Spain >> were here of the era, and seventy seven hundred people are here for the KubeCon Cloud NativeCon, twenty, nineteen, Off student. My co host for the two days of coverage is Corey Quinn, and joining Me are the two co chairs of this CNC event. Janet Cooper, who is also thie, suffer engineer with Google and having done the wrap up on stage in the keynote this morning, find Lyle's a senior staff engineer with BM where thank you both for joining us, >> Thank you. >> Thanks for having me. >> So let's start. We're celebrating five years of Kubernetes as damn calm laid out this morning. You know, of course, you know came from Google board in over a decade of experience there. So it just helps out the state for us. >> Um, so I started working on communities since before the 1.4 release and then steal a project Montana today. And I feel so proud to see, uh, the progress off this project and its has grown exponentially. And today we have already thirty one thousand contributors and expect it to grow even more if you can. >> All right. So, Brian, you work with some of the original people that helped create who Burnett ease because you came to be and where, by way of the FTO acquisition, seventy seven hundred people here we said it. So it's, you know, just about the size of us feel that we had in Seattle a few months ago Way Expect that San Diego is going to be massive when we get there in the fall. But you know, talk to us is the co chair, you know, What's it mean to, you know, put something like this together? >> Well, so as ah is a long time open source person and seeing you know, all these companies move around for, you know, decades. Now it's nice to be a part of something that I saw from the sidelines for so, so long. I'm actually... it's kind of surreal because I didn't do anything special to get here. I just did what I was doing. And you know, Jan and I just wound up here together, so it's a great feeling, and it's the best part about it is whenever I get off stage and I walked outside and I walked back. It's like a ten minute walk each way. So many people are like, Yeah, you really made my morning And that's that's super special. >> Yeah. I mean, look, you know, we're we're huge fans of open source in general and, you know, communities, especially here. So look, there was no, you know, you both have full time jobs, and you're giving your time to support this. So thank you for what you did. And, you know, we know it takes an army to put together in a community. Some of these people, we're Brian, you know, you got upstate talk about all the various project. There's so many pieces here. We've only have a few minutes. Any kind of major highlights You wanna pull from the keynote? >> So the biggest. Actually, I I've only highlight won the open census open. Tracing merge is great, because not only because it's going to make a better product, but he had two pretty good pieces of software. One from Google, actually, literally both from Google. Ultimately, But they realize that. Hey, we have the same goals. We have similar interfaces. And instead of going through this arms race, what they did is sable. This is what we'LL do. We'LL create a new project and will merge them. That is, you know, that is one of the best things about open source. You know, you want to see this in a lot of places, but people are mature enough to say, Hey, we're going to actually make something bigger and better for everyone. And that was my favorite update. >> Yeah, well, I tell you, and I'm doing my job well, because literally like during the keynote, I reached out to Ben. And Ben and Morgan are going to come on the program to talk about that merging later today. That was interested. >> I've often been accused of having that first language being snark, and I guess in that light, something that I'm not particularly clear on, and this is not the setup for a joke. But one announcement that was made on stage today was that Tiller is no longer included in the current version of Wasn't Helm. Yes, yes, And everyone clapped and applauded, and my immediate response was first off. Wow, if you were the person that wrote Tiller, that probably didn't feel so good given. Everyone was copping and happy about it. But it seems that that was big and transformative and revelatory for a lot of the audience. What is Tiller and why is it perceived as being less than awesome? >> All right, so I will give you a disclaimer, >> please. >> The disclaimer is I do not work on the helm project... Wonderful >> ...so anything that I say should be fact checked. >> Excellent. >> So Well, so here's the big deal. When Tiller, when Helm was introduced, they had this thing called Tiller. And what tiller did was it ran at a basically a cluster wide level to make sure that it could coordinate software being installed and Kubernetes named Spaces or groups how Kubernetes applications are distributed. So what happens is is that that was the best vector for security problems. Basically, you had this root level piece of software running, and people were figuring out ways to get around it. And it was a big security hole. What >> they've done Just a component. It's an attack platform. It >> was one hundred percent. I mean, I remember bit. Nami actually wrote a block post. You know, disclaimer of'em were just bought that bit na me. >> Yes, I insisted It's called Bitten, am I? But we'LL get to that >> another. This's a disclaimer, You know, There Now you know there now my co workers But they wrote they were with very good article about a year and a half ago about just all the attack vectors, but and then also gave us solution around that. Now you don't need that solution. What you get by default. Now something is much more secure. And that's the most important piece. And I think the community really loves Helm, and now they have helm with better defaults. >> So, Janet, a lot of people at the show you talk about, you know, tens of thousands of contributors to it. But that being said, there's still a lot of the world that is just getting started. Part of the key note. And I knew you wrote something running workloads and cover Netease talk a little bit about how we're helping you know, those that aren't yet, you know, on board with you getting into the community ship. >> So I work on the C gaps. So she grabs one of the sub fracture that own is the work wells AP Eyes. That's why I had that. What post? About running for closing covered alleys. So basically, you you're using coronaries clarity, baby eyes to run a different type of application, and we call it were close. So you have stay full state wears or jobs and demons and you have different guys to run those clothes in the communities. And then for those who are just getting started, maybe start with, uh, stay last were close. That's the easiest one. And then for people who are looking Teo, contribute war I. I encouraged you to start with maybe small fixes, maybe take some documents or do some small P R's and you're reputations from there and star from small contributions and then feel all the way up. >> Yeah, so you know, one of one of the things when I look out there, you know, it's a complex ecosystem now, and, you know, there's a lot of pieces in there, you know, you know, trend we see is a lot of customers looking for manage services. A lot of you know, you know, I need opinions to help get me through all of these various pieces. You know what? What do you say to those people? And they're coming in And there's that, you know, paradox of choice When they, you know, come, come looking. You know, all the options out there. >> So I would say, Start with something simple that works. And then you can always ask others for advice for what works, What doesn't work. And you can hear from their success stories or failure stories. And then I think I recently he saw Block post about Some people in the community is collecting a potential failure stories. There is also a talk about humanity's fellow, the stories. So maybe you can go there and learn from the old those mistakes and then how to build a better system from there. >> I'd love that. We have to celebrate those failures that we hopefully can learn from them. Find anything on that, You know, from your viewpoint. >> Eso Actually, it's something I research is developer experience for you. Bernetti. So my communities is this whole big ping. I look on top of it and I'm looking at the outside in howto developers interact with Burnett, ese. And what we're seeing is that there's lots of room for opportunities and Mohr tools outside of the main community space that will help people actually interact with it because that's not really communities. Developers responsibility, you know, so one anything that I think that we're doing now is we're looking and this is something that we're doing and be aware that I can talk about is that we're looking at a P ice we're looking at. We realize that client go, which is the way that you burnett ese talks with sapi eyes, and a lot of people are using out externally were looking at. But what does it actually mean for human to use this and a lot of my work is just really around. Well, that's cool for computers. Now, what if a human has to use it? So what we're finding is that no. And I'm going to talk about this in my keynote tomorrow. You know, we're on this journey, and Kubernetes is not the destination. Coover Netease is the vehicle that is getting us to the destination that we don't even know what it is. So there's lots of spaces that we can look around to improve Kubernetes without even touching Cooper Netease itself, because actually, it's pretty good and it's fairly stable in a lot of cases. But it's hard, and that's the best part. So that's, you know, lots of work for us, the salt >> from my perspective. One of the turning points in Kou Burnett is a success. Story was when it got beyond just Google. Well, folks working on it. For better or worse, Google has a certain step of coding standards, and then you bring it to the real world, where there are people who are, Let's be honest, like me, where my coding standard is. I should try to right some some days, and not everything winds up having the same constraints. Not everything has the same approach. To some extent, it really feels like a tipping point for all of it was when you wind up getting to a position where people are bringing their real world workload that don't look like anything, anyone would be able to write a googol and keep their job. But still having to work with this, there was a wound up being sort of blossoming effect really accelerating the project. Conversely, other large infrastructure projects we need not mention when they had that tipping point in getting more people involved, they sort of imploded on themselves. I'm curious. Do you have any thoughts as to why you Burnett? He started thriving where other projects and failed trying to do the same things. >> I have something you go first. And >> I think the biggest thing about cybernetics is the really strong community and the ecosystem and also communities has the extensive bility for you to build on top of communities. We've seen people building from works, and then the platform is different platforms. Open source platforms on top of you. Burnett is so other people can use on other layers. Hyah. Layers off stacks on top of fraternities. Just use those open source. So, for example, we have the CRD. It's an A P I that allows you to feel your own customized, overnighted style FBI, so they're using some custom for couple databases. You could just create your own carbonated style FBI and call out your database or other stuffs, and then you can combine them into your own platform. And that's very powerful because everywhere. I can just use the same FBI, the Carbonari style idea to manage almost everything and that enables a Teo be able to, you know, on communities being adopted in different industry, such as I o t. A and Lord. >> So actually, this is perfect because the sleaze and so what I was going to say The secret of community is that we don't talk about actually job, Ada says. It's a lot, but it's a communities is a platform for creating platforms. So Kubernetes really is almost built on itself. You can extend Cooper. Netease like communities extends itself with the same semantics that it lets users extended. So Janet was talking about >> becoming the software that is eating the world. Yeah, it >> literally is. So Janet talked about the CRD sees custom resource definitions. It's the same. It's the same mechanism that Kubernetes uses to add new features. So whenever you're using these mechanisms, you're using Kou Burnett. He's basically the Cooper Nate's infrastructure to create. So really, what it is is that this is the tool kit for creating your solutions. What is why I say that Kubernetes is not an end point its its journey. >> So the cloud native system. >> So you know what? Yeah, and I like I like the limits analogy that people talk about. Like Coburn. Eighties is is like clinics. If you think about how Lennox you know little l. Lennox. Yeah. You know, I'm saying little l olynyk sub Let's put together. Yeah, you Burnett. He's like parts of communities would be system. And it's it's all these components come together the creature operating system, and that's the best part about it. >> Okay, so for me, the people that are not the seventy seven hundred that air here give them a little bit of, you know, walk around the show and some of the nooks and crannies that they might not know, like, you know, for myself having been to a number of these like Boy, there were so many half day and full day workshops yesterday there were, like, at least, like fifteen or seventeen or something like that that I saw, You know, obviously there's some of the big keynote. The Expo Hall is sprawling it, you know, I've been toe, you know, fifteen twenty thousand people show here This sex Bohol feels is bustling ahs that one is and well as tons of breakout session. So, you know, give us some of the things that people would have been missing if they didn't come to the show here. >> So just for the record, if you missed the show, you can still watch all the videos online. And then you can also watch the lifestream for keynotes so on. I personally love the applicant the different ways for a customizing covered at ease. So there's Ah, customizing overnight is track. And also there's the apple that applications track and I personally love that. And also I like the color case studies So you can't go to the case studies track to see on different users and users off Cooper, Natty shared. There were war stories, >> Yes, So I think that she will miss. There's a few things that you'll miss if you if you're not here in Barcelona right now, the first thing is that this convention center is huge. It's a ten minute walk from the door to where we're sitting right now, but more seriously, one. The things you'LL miss is that before the conference starts, there are there are a whole bunch of summits, Red had had a summit and fewer people had some. It's yesterday where they talk about things. There's the training sessions, which a lot of cases aren't recorded. And then another thing is that the special interest groups, the cigs. So Cooper ninety six, they all get together and they have faced the face discussions and then generally one from yesterday We're not. We're not recorded. So what you're missing is the people who actually make this big machine turn. They get together face to face and they first of all, they built from a rotary. But they get to discuss items that have require high bit of bandwith that you really can't do over again of issue or email, or even even a slack call like you can actually get this thing solved. And the best thing is watching these people. And then you watch the great ideas that in, you know, three, six months to a year become like, really big thing. So I bet yesterday, so something was discussed. Actually, I know of some things that we discussed yesterday that might fundamentally change how we deal with communities. So that's that is the value of being here and then the third thing is like when you come to a conference like this, where there's almost a thousand people, there's a lot of conversations that happened between, you know, the Expo Hall and the session rooms. And there's, um there's, you know, people are getting jobs here, People are finding new friends and people are learning. And before thing and I'll end with This is that I walk around looking for people who come in on the on the diversity scholarships, and I would not hear their stories if I did not come. So I met two people. I met a young lady from New Zealand who got the scholarship and flew here, you know, and super smart, but is in New Zealand and university, and I get to hear her insights with life. And then I get to share how you could be better in the same thing. I met a gentleman from Zimbabwe yesterday was going to school and take down, and what I hear is that there's so many smart people without opportunities, so if you're looking for opportunities, it's in these halls. There's a lot of people who have either money for you or they have re sources were really doesn't have a job or just you know what? Maybe there's someone you can call whenever you're stuck. So there is a lot of benefit to come into these. If you can get here, >> talent is evenly distributed. Opportunity is not. So I think the diversity scholarship program is one of the most inspirational things I saw mentioned out of a number of inspirational things that >> I know. It's It's my favorite part of communities. You know, I am super lucky that I haven't employees that our employer that can afford to send me here. Then I'm also super lucky that I probably couldn't afford to send myself here if I wanted to. And I do as much as I can to get people >> here. Well, Brian and Janet thank you so much for all you did to put this and sharing it with our community here. I'Ll repeat something that I said in Seattle. Actually, there was a lot of cloud shows out there. But if you're looking for you know, that independent cloud show that you know, lives in this multi hybrid cloud, whatever you wanna call it world you know this is one of the best out there. And the people? Absolutely. If you don't come with networking opportunities, we had into it on earlier, and they talked about how you know, this is the kind of place you come and you find a few people that you could hire to train the hundreds of people inside on all of the latest cloud native pieces. >> Can I say one thing, please? Brian S O, this is This is significant and it's significant for Janet and I. We are in the United States. We are, you know, Janet is a minority and I am a minority. This is the largest open source conference in the world. Siri's This is the largest open source conference in Europe. When we do, when we do, it ended a year. Whenever we do San Diego, it'Ll be the largest open source conference in the world. And look who's running it. You know, my new co chair is also a minority. This is amazing. And I love that. It shows that people who look like us we can come up here and do these things because like you said, opportunity is is, you know, opportunities the hard thing. Talent is everywhere. It's all over the place. And I'm glad we had a chance to do this. >> All right. Well, Brian, Janet, thank you so much for all of that. And Cory and I will be back with more coverage after this brief break. Thank you for watching the cues.

>> Announcer: Live from Copenhagen, Denmark, it's the CUBE, covering KubeCon and Cloud Native Con Europe 2018. Brought to you by the Cloud Native Computing Foundation and its ecosystem partners. (busy music) >> Welcome back, everyone, live here in Copenhagen, Denmark, it's the CUBE's coverage of KubeCon 2018. I'm John Furrier, the host of the CUBE, along with Lauren Cooney, who's the founder of Spark Labs. She's been co-host with me two days, two days of wall to wall coverage. Stephan Fabel, Product Strategy Lead at Canonical, is here inside the CUBE, and from San Francisco. Again, welcome to the CUBE, thanks for coming. >> Thank you, thanks so much for having me. >> I've got to, you guys have been around the block, you know about open source software platforms, you get and do it for a while. Interesting time here at KubeCon. Kubernetes, Istio, Kubeflow, Cloud Native, they've still got the brand name CloudNativeCon and KubeCon. Modern application architecture's now in play. I see this notion of an interoperability model coming in that's certainly going to be a de facto standard. People are already kind of declaring it a de facto standard. It really shows a path to multi-cloud, but also frees up developers from a lot of the heavy lifting. Lou Tucker from Cisco was saying they don't want to do networking. Let's just have that be infrastructure as code, that's DevOps, that's what we want. >> Stephan: That is exactly right. >> What are you guys doing here? What's the story with Canonical and how does that fit into the megatrends? >> Yeah, I mean, there's a couple of things that we at Canonical always believe to be one of the core sort of tenets in our distribution of Kubernetes. As you know, we've been very active in this space fairly early on, and have been an active distributor of Kubernetes and a certified distributor of our version of Kubernetes. Pure upstream, remain conformant to the main public clouds, such as to enable that workload migration and mobility from on prem up to any of the other providers to accommodate all kinds of use cases, right. >> You guys made a bet on Kubernetes, obviously, good call. >> Stephan: Right. >> Right. What's the progress now, what's next? Because that's, the bets are paying off. I saw Red Hat had a great bet with what they did with Kubernetes, changed what OpenShift became. You guys had a bet in Kubernetes, what has that become for Canonical? >> Yeah, so based on the pure upstream distribution that we have, we really feel that enabling the ecosystem in a standards compliant way so that all of the landscape projects that are part of the CNCF can be deployed on top of Kubernetes, on top of our distribution of Kubernetes in just the same way that they would be developed or deployed in any of the large containers of service offerings that are out there is one of the big benefits that our customers would gain from using our Kubernetes. >> What's your differentiator for the distribution of Kubernetes that you have versus others? >> Well, there's two. The first one, I think, is the notion that deploying Kubernetes on premise is something that you want to do in a repeatable fashion, operationally efficient with the right capex opex mix, so we believe that there is a place for Kubernetes as a product, just deploy it, it works on any substrate that you've got available to you. But then also, for mainstream America, right, you may want to have a managed service on top of Kubernetes as well. We offer that, too, just a way to get started and kick the tires and see where that takes you as far as the developers are concerned. Now, on prem, you will find that there are a couple of challenges when deploying Kubernetes that are really the key differentiator. The first one, I would say, is things like integration into the storage that's local, integration into the network that's local, and integration into all of those services that should be available in the Cloud Native microservices architecture platform, such as low bouncers, right, elasticity, object store, etc. The second, and most importantly, because it is a key enabler for those next generation workloads, is the GPGPU enablement work that we're doing with partners such as NVIDIA. When you deploy the Canonical distribution of Kubernetes, you actually get the NVIDIA acceleration out of the box the way that NVIDIA envisions this on top of Kubernetes and the way that it is, by the way, being deployed on the public clouds. >> You bring a lot of your goodness to the table inside the Kubernetes distribution. OK, what are some customers doing? Give some use cases of some customers' Kubernetes, what are some of the things that they're doing with it, what's the early indication? What's the feedback? >> Sure. We have a ton of customers that are using our version of Kubernetes to do the machine learning applications and the AI of the next gen workloads in use cases such as smart cities or connected cars, where, when you look at self-driving cars, right, as the next gen that's coming out of the valley, they put in 300,000, 150,000, 400,000 miles a year on the road these days just optimizing the models that are being used to actually take over one day. Enabling those kinds of workloads in a distributed fashion requires DevOps expertise. Now, the people who are actually writing those applications are not DevOps people, they're data scientists, right. They shouldn't have to learn how to deploy Kubernetes, how to create a container and all those things. They should just be able to deploy the application on top an attractive substrate that actually supports that distributed application use case, and so that is where we come in. >> This is interesting, because what you're basically doing is making an application developer a DevOps developer overnight. >> Stephan: That's exactly right. >> That's really important. I was just talking with the co-chair of CNCF. We're talking about, Liz Rice and I were talking about why everyone's so, like, excited here. One of the things I said was, because people who are doing DevOps were hardcore, and they had to build everything from scratch, and all the scar tissue. But the benefits, once you got through the knothole there, the benefits were amazing, right. You go, okay, you don't want to do that again, but now there's a way to make it easier. There's kind of a shared experience even though no one's met each other, so there's kind of a joint community. >> I agree. I think it is increasingly about enabling developers who are experts in their field to actually leverage Kubernetes and the advantages that it brings in a more intuitive fashion. Just take it up a notch. >> How did the Kubernetes vibe integrate in with Canonical? I'm sure, given the background of the company, it probably was a nice fit, people embraced it. You guys were early. >> Stephan: Yeah. >> What's the internal scuttlebutt on the vibe with Kubernetes? >> Oh, we love Kubernetes as a technology. Ubuntu was always close to the developer and close to where the innovation happens. It was a natural fit to actually support all that workflow now in this new world of Kubernetes. We embraced OpenStack for the same reason, and in a similar fashion, Kubernetes has really driven the point home, containerist applications with a powerful orchestration framework such as Kubernetes are the next step for all the developers that are out there, and so as a consequence, this was a perfect match. >> It's also a no-brainer if you think about it, software methodology moving to the next level. This is total step up function for productivity for developers. That's really a key thing. What's your observation of that trend? Because at the end of the day, there's now Kubernetes, which does a lot of great things, but one of the hottest areas is Istio service meshes, and then you've got Kubeflow orchestration, a lot of other things that are happening around Kubernetes. What are you guys seeing that's important for Canonical's customers, what you're doing product wise. Where's the order of operations, what's next? What are you guys focused on, what's the priorities? >> Well, our biggest priority right now is enabling things like Kubeflow, which, by the way, are also using Istio internally, right, to actually enable those data scientists who actually deploy their I workload. We work very closely with Google to try and enable this in an on prem fashion out of the box which is something you can actually do today. >> John: You guys are doing this now inside this. >> We're doing this right now. This is also where we're going to double and triple down. >> This is actually your best practice, too, if you think about it, you want to take it in house, and then get a feel for it. What's the internal vibe on that, positive? >> Oh, absolutely. I mean, we always saw infrastructure as code and actually as intelligent infrastructure as something that we wanted to build our conceptual framework around, so very concretely, right. We've always had this notion of composable building blocks adding up to, sum of one being greater than two, right, like those types of scenarios. Actually using things like Kubernetes as an effective building block to then build out web applications that use things like machine learning algorithms underneath, that's a perfect use case for a next gen workload, and also something that we might use ourselves internally. >> Well, hey, that whole building block thing, it's happening. >> Stephan: Yeah. >> News flash. >> Stephan: Exactly, right? >> I mean, it's almost a pinch me moment for the people in the industry like, oh my god, it's going to go to a whole other level. How do you guys envision that next level going? Beyond the building blocks, is it, I mean, what's the vision that you guys have? Obviously, infrastructure as code programmability, but now, you're talking about infrastructure as code was great, but now you've got microservices growth coming on top of it, it's a services market now. >> It is, it is. I think that the biggest challenge will be the distribution of the workloads, right. You have edge compute coming along in the telco space, you have, like I said, smart cities, right, the sensors will be everywhere, and they will feed data back, and how do you manage that at scale, right? How do you manage that across various different hardware perspectives? We have hardware platforms such as ARM 64 picking up, right, and actually playing a very significant role at the edge, and increasingly, even in the core. We've always believed that providing that software and the distribution of IS such as Kubernetes and others on top of those additional architectures would make a huge difference, and that is clearly paying off. What we see is, the increased need of managing hybrid workloads across multi-cloud scenarios that could be composed of different architectures, not just x86, the future is not homogeneous at all. It'll be all over the place. All those use cases and all those particular situation require that building block principle, like all the way from the OS up to the application. >> John: That's a great use case for containers. Kubernetes, Istio, Kubeflow. >> Absolutely. >> All stacking in line beautifully from an evolution standpoint. I've got to ask you a personal question. I mean, I was at Canonical, great company, I want to thank Canonical for being a sponsor of the CUBE over the years. We've had Mark Shuttleworth on the CUBE had an OpenStack going way back when. You guys are a great participant in the community as a company and the people there been phenomenal. You're new. >> I'm new. >> What attracted you to Canonical? What was the motivating force? What drew you in? You're now running Products, a big job. You've got a lot in front of you. Obviously, it's a great market, so you're a great company. Just share, just color and why Canonical, what attracted you there? >> I've always been a user of Ubuntu, I've been a user since the first hour. I've used Ubuntu in my research. I did robotics based on Ubuntu way before it was cool. I built all kinds of things on top of Ubuntu throughout my entire career. Working for Canonical, which is a company that always exhibited great vision into the future and great predictions into trends that would prove to become true was just, for me, something that was very attractive. >> Their leadership has a good eye on the prize. They had good 20 mile stare, as we say, they can see the roadmap ahead and then make either course corrections or tweaks. >> Yeah. >> Great, awesome. Well, I mean, what's new there? What's your, take a minute to explain what's new at Canonical, role here at KubeCon, what are some of the conversations you're having? >> Yeah, so I mean, for us at KubeCon, it's always been an important part of our outreach to the community, great opportunity for us to have great conversations with our partners in the field. I think it is really about enabling the ecosystem in a more straightforward way. There's no better place to have those types of conversations than here, where everybody comes together and really establishes those relationships. For us, it is about, again, enabling the developer and really staying close to that innovation and supporting that in an optimal way. Yes, I mean, that, to us, is the role that we play. You've got a lot of end users here who are building stuff. >> Oh, absolutely, yeah. They, I mean, I had a talk today about Kubeflow with Google, and after the talk, lots of folks came up to me and said, hey, how can I use this at home, right? >> Sometimes with, whether it's timing, technology, all the above, Kubernetes really hit it strong with the timing, industry was ready for it. Containers had a nice gestation period. People know about containers. >> Stephan: Absolutely. >> Engineers know containers, know about those kinds of concepts. Now we're at a whole other operating environment. >> Stephan: Absolutely. >> You guys are at the forefront. Thanks for coming on the CUBE. >> Oh, thank you, I appreciate it. >> Stephan sharing the perspective, Stephan Fabel. Running Product and Strategy for Canonical, building stuff, this is what's going on in Kubernetes in KubeCon, end users are actually building and orchestrating workloads. Multi-cloud is what people are talking about and the tech to make it happen is here. I'm John Furrier with the CUBE. Stay with us for more live coverage here at KubeCon 2018, part of the CNCF CUBE coverage. We'll be right back after this short break. (busy music)

>> Narrator: Live, from Copenhagen, Denmark, it's theCube. Covering KubeCon and Cloud Native Con Europe 2018. Brought to you by the Cloud Native Computing Foundation and its ecosystem partners. >> Hello, everyone, welcome back to theCUBE exclusive coverage of CNCF. The Cloud Native Foundation, Compute Foundation, part of the Linux Foundation of KubeCon 2018 here in Copenhagen, Denmark. I'm John Furrier co-host of theCUBE here with analyst this week Lauren Cooney, who is the founder of Spark Labs, brand new start up that she founded to help companies bring innovation to Cloud Native, bring in all of her expertise to companies. Also, here on theCUBE, Lauren, great to have you this week. >> Thanks, John. >> Here in Europe, you've done so much work in the area of open source over the years. You've done, you were radical renegade, progressive, pushing PHP, bringing that to Microsoft. Doing a lot of great things, and now we're in a new modern era, and you're bringing that expertise, but you're also on the front lines of the new wave. >> Lauren: Definitely. >> Cloud Native, so what's your take? What's your analysis? I mean, there's so much going on. You can't just retrofit old school open source, but it's got to build on the next generation. What's your thoughts? >> It has to build on the next generation, but you also have to look back at what has happened in the past. I think what is incredibly important to see is the mistakes that have been made in the past, so that people don't repeat them. One of the things that I'm seeing here and hearing a lot about is multiple distributions of Kubernetes out there, and when I hear multiple distributions I get worried that they're going the open sack route and there is going to be too many distributions out there. I would rather see one or two standard become kind of more standard and people building on top of that. I think it's the right way to go versus the splintering of the community. If the community is going to stay together you're going to have to narrow that down. >> What's the rationale for the distribution? Because, we've seen this before. Certainly at Hadoop, we saw people come out with distros and then abandon them, and then people coalesce around. >> Oh, they'll just die on the vine. I mean, fundamentally they just will die on the vine. It won't be, if it's not de facto already you're probably not going to get it de facto. >> John: What should companies do? Should they have a distro down. >> They should map to one of the key distros right now. They should, basically, use what is out there already. The one that they feel is right, and for their users, and for their company long term. >> I really enjoyed a couple of interviews we had yesterday. I want to just kind of revisit a couple of them. Tyler and Dirk, we had Tyler on from the new programming language ballerina that was launched. He's part of WSO2. Dirk is from Vien, where former early Linux guy, Linux foundation guy, worked with Linux tarballs in the early days. These guys know up the source. So you look at some of those leaders, and they say, "Hey, this is about the people" What are the things that we can draw from the past that are still relevant today? As the new formula of Kubernetes horizontally scalable cloud, Cloud Native thousands and, potentially, millions of micro-services coming online, new kinds of dynamic policy based infrastructure software, everything's coming. >> Service mesh, can't forget service mesh. >> Service meshes are going to be huge. What do we have to keep and preserve, and what is being built out that's new? >> Well, I think that you need to preserve the feeling of the community and what's going on there. I mean, these communities, actually it's communities not community, and these folks are coming along for the wave right? And I think it's important to make sure that people are aware of that, and there's lots of different personalities and lots of different goodness that can be brought to the table with that and the recognition of that. I also think that, for the most part, I do believe that this is one of the strongest communities out there, and it will continue to be for a number of years. >> I want to get your thoughts on something Ed Warnicke said from Cisco because he was very complimentary of the CNCF as are other people, and we have been complimentary as well about keeping everything tight to the core and allowing people to innovate. So you have, and we have commented on theCUBE and other KubeCons about this, and they've been doing it, which is let the innovation foster on the technical side as well as let people flex their business model opportunities. >> Lauren: Definitely. >> Not so much just for the sake of commercialization because if you have too much commercialization you might stunt the community of growth organically so there's a balance, and I think CNCF has done a good job there, but they've kept the core of Kubernetes really tight which has allowed the de facto standard approach to be Kubernetes. That has created great opportunity, and people are super excited by that. What's your analysis of what happens next? What needs to happen? What's the momentum phase two of this? >> I think part of it is, how do you monetize, right? It's looking at, and this is part of what Spark Labs actually does, is we actually work with companies, some that are in the CNCF, and we work on them in different ways to monetize. Is it a services wrapper that's going to work? Is it additional features or functionality? The innovation comes with the technology, but with that technology you have to have the business model kind of in mind when you're building this out so you can figure out how to make money. As these smaller companies especially are looking to do and some of the bigger companies as well. >> I really think it's important for the CNCF and the Linux foundation and I know they're on this so its not critical analysis so much as it is more of an observation. You have a long tail of start ups and kind of a fat tail if you will, that are out there, and you have the big whales out there Google, Microsoft, Amazon, and others at the top. There was a comment in Austin, a snarky comment. I won't say by who, but I was looking at the logo board of the sponsors, and the guy said, "All those start-ups, they might be dead in 18 months" and it made me pause and say okay, that's an observation because they were brand new companies. >> Lauren: Mm hmm. >> That can't happen. We need to have a model of preservation for start-ups to experiment, to grow. This is something you're doing at Spark Labs so what's your view of this? And, reaction to the fact that this has to happen. What can we do as an industry and community to make sure the start ups-- >> I think the Linux foundation is doing one of the best things that can be done out there. Other open source foundations do too. Is they create the infrastructure so that folks have the support for marketing, or legal, or something along those lines, but so companies are allowed to innovate and then the Linux Foundation basically bets on the innovation and they bet on multiple innovations with multiple companies so they allow these companies to thrive while giving them the support inside of that. >> John: Yeah. >> And I think that's really helping a lot of these companies along. >> Well, Dave Collins always says is the membership organization, so no members no business model so I mean they're incented to make sure that, or hope, that these guys can survive, and certainly there's going to be some misfires and people will natural evolution. So what are you most excited about? I got to ask ya, I mean you're out on your own now. Congratulations, you started up. >> Thank you. >> Super exciting for you and I'm happy that you're going to go out on your own. What are some of the things you're excited about? What are you digging your teeth into, in terms of projects? Share what you're doing. >> I'm super excited about these companies that are coming out with true multi-cloud. So, allowing applications to run across multiple environments, public, private, et cetera. And we've been saying we can do it for a decade or something like that, but fundamentally that wasn't the case. You did have to re-write code. You did have to do a lot of underlying things to make that occur. One of the things that I'm super excited about is being able to take those companies and figure out how to actually get their product to market faster. Some of these guys are still in stealth. They need to move really fast if they want to catch up. I also love working with them on figuring out how to build out their teams, figuring out how to monetize. What are the next steps? What are the business plans, really, behind this? What is the one, three, five year model that they're going to use? I also love helping them get the money, of course. I think that's the fun part too. >> Yeah, it's always fun. Start-ups are great. What I'm excited about, I got to tell ya, I got to share with you just some personal feelings. I love this market right now because I've seen many waves of innovation and I think this wave of cloud native, whatever you want to call it this massive wave or sets of waves coming in and you got blockchain and other things going on behind it these centralized applications which I think is part of this set coming in, is that it's bigger than all the other waves combined and because there's so much value creation on the horizon and I think historically, this moment in time, historically is going to be a point we're going to look back and say the Kubernetes de facto standard galvanized a set of industry, a new card of players who are going to establish a new way methodology of doing things, and we're documenting it. Secondly, the role of community, as you pointed out, is so important here, and it's strong, but now we're living in a new age of digital. We're seeing formations of new kinds of community engagement digitally, not just the events, so I'm excited with theCUBE and what we're doing here, and what the Linux Foundation is doing because there's now going to be, potentially, exponential growth and acceleration around the combination of community. >> Yup. >> The community growth with this new modern commercialization on digital. >> It's definitely increasingly important, and you have to look at it from the technologies making it happen. The technology is looking at, edge computing is going to make digital happen really when you look at all the end points and things along those lines. And, I think that it's going to be great for everyone involved in that. >> Yeah, and we can learn a lot from looking at the Facebook example of how fake news swayed the election. How people were weaponizing content for bad things. There's also an opposite effect, we believe that you can do the for good. >> Lauren: Totally agree. >> I think digital will have a big role in the next generation community formations, community growth, short cuts to the truth, really that's what it's all about. It's about the people, so certainly we're going to be documenting it. Thanks for your commentary. >> Lauren: Definitely. >> Appreciate it, great to work with you this week. Day two of exclusive coverage, here at the Linux Foundation's Cloud Native Compute Foundation's, CNCF's KubeCon 2018. This is where Kubernetes, service mesh, Istio a lot of great projects, from a lot of smart people. We're here on the ground covering it live. Day two, we'll be back with more coverage. Stay with us for day two coverage, after this short break. (electronic music)