 Hey everybody, welcome back. Good afternoon. Lisa Martin here with John Furrier live into Detroit, Michigan. We are at KubeCon CloudNativeCon 2022 North America. John, this is nearing the end of our second day of coverage. And one of the things that has been breaking all day on this show is news. We have more news to break back. This next segment is a company we've been following. They got some news we're going to get into. Managing Kubernetes' life cycle has been a huge challenge when you've got large organizations whether you're spinning up and scaling. Scale is the big story. Kubernetes is the center of the conversation. This next segment is going to be great. It is. We've got two guests from Spectre Cloud here. Please welcome its CEO, Chen Rui Fu, a co-founder. And it's CTO, a co-founder, Stad Malik. Guys, great to have you on the program. Thank you for having us. My pleasure. So, Chen Rui, what's going on? What's the big news? Yeah, so we just announced our Palace 3.0 this morning. So we add a bunch of new functionality. So first of all, we have a nested cluster. So enable enterprise to easily provide Kubernetes service even on top of the existing clusters. And secondly, we also support seamless migration for the existing cluster. We enable them to be able to migrate their cluster into our CNCF upstream Kubernetes distro called Palette Extended Kubernetes PXK without any downtime. And lastly, we also add a lot of focus on developer experience. Those additional capability enable developer to easily onboard and deploy the application for DevTest and troubleshooting without they have to have a steep Kubernetes landing code. So big breaking news this morning, Palette 3.0. So you got the product. This is a big theme here. Developer productivity, ease of use is the top story here as developers are going to increase their code velocity because they're under a lot of pressure. This infrastructure is getting smarter. This is a big part of managing it. So the toil is now moving to the ops teams. They're now dev teams, security. You got to enable faster deployment of apps and code. This is what you guys saw while you're getting this right. That take us through that specific value proposition. What's the, one of the key things in this news release? Yeah, exactly right. So we basically provide our solution to platform engineering team so that they can use our platform to enable Kubernetes service to serve their developers and their application team. And then in the meantime, the developers will be able to easily use Kubernetes or without they have to learn a lot of Kubernetes specific things. So maybe you can get into something. Yeah, an option. So the detail about it is there's a big separation between what operations team does and development team that are using the actual capability. The development teams don't necessarily to know the internals of Kubernetes. There's so much complexity when it comes into it. How do I do things like deployments, pause, manifest, just too much? So what our platform does, it makes it really simple for them to say, I have a containerized application. I want to be able to model it. It's a really simple profile. And from there, be able to say, I have a database service I want to attach to it. I have a specific service. Go run it. Behind the scenes, does it run inside of a nested cluster which we'll talk a little bit. Does it run in the host cluster? Those are happening transparently for the developers. You know what I love about this what you guys are doing in the news? It really points out what I love about DevOps. Because cloud, let's face it, cloud early adopters were all the hardcore cloud folks. As it goes mainstream with Kubernetes, you start to see like words like platform engineering. And I love that term. That means there's a platform. It's been around for a while for people who are building their own stuff. That means it's going to scale and enable people to enable value, build on top of it, move faster. This platform engineering is becoming now a standard in enterprises. It wasn't like that before. What's your eyes for reactors? How do you see that evolving faster? Or do you believe that? Or what's your take on it? Yeah, so I think it's starting from the DevOps team, like that every application team, they all try to deploy and manage their application under their own Kubernetes infrastructure. But very soon, each application team, they start realize they have to repetitively do the same thing. So these will need to have a platform engineering team to basically bring some of the common practice to that. And some people call them SREs, like that's really platform engineering. It is, it is. If you think about like SREs, the ability to deploy your applications at scale and monitoring observability, I think what platform engineering does is codify all those best practices. Everything when it comes about how do you monitor the actual applications, how do you do the CI CD, your backups, instead of now having every single individual development team figuring out how to do themselves, platform engineering is saying, why don't we actually build policies that we can provide as a service to different development teams so that they can operate their own applications at scale? So launching Pellet3.0 today, you also had a launch in September, so just a few weeks ago. Talk about what these two announcements mean from Spectre Cloud's perspective in terms of proof points, what you're delivering to the end users and the value that they're getting from it. Yeah, so our goal is really to help enterprise to deploy and around Kubernetes anyway. Whether it's in cloud data center or even at edge locations. So in September, we also announced our 8V2 capabilities which enable very easy deployment of edge Kubernetes at any location like a retail stores, restaurant, so on and so forth. So as you know, at edge location, there's no cloud endpoint there. It's not easy to directly deploy and manage Kubernetes. And also at edge location, it's not as secure as cloud data center environment. So how to make the end-to-end system more secure, that it's tempo-proof, that is also very, very important. Right, great take there. Thanks for explaining that. I got to ask, cause I'm curious, what's the secret sauce? Is it nested clusters? What's the core under the hood here on 3.0 that people should know about? It's news, it's hot, what's the most important? To be honest, it's about enabling developer velocity. Now how do you enable developer velocity? It's going to be able for them to think about deploying applications without worrying about Kubernetes, being able to build these application profiles. This nested cluster that we're talking about enables them to get access to a complete cluster within seconds. They're essentially having access to be able to add any operations, any capabilities without having the ability to provision a cluster inside an infrastructure, whether it's Amazon, Google or on-prem. And you have the Dev Engine too, right? That's a self-service provisioning for environments, is that? Yeah, so the Dev Engine itself are the capabilities that we offer to developers so that they can build these application profiles. What the application profiles, again, they define aspects about my application is going to be a container, it's going to be a database service, it's going to be a helm chart. They define that entire structure inside of it. From there, they can choose to say, I want to deploy this. The target environment, whether it becomes an actual host cluster or a nested cluster itself, is irrelevant to them. For them, it's completely transparent. So transparency, enabling developer velocity, what's been some of the feedback so far? Oh, all the developers love that. And also, same for all the ops teams. If it's easy and goes faster, it reduces the steps. Because the ops teams, they need a consistency, they need a governance, they need visibility, but in the meantime, developers, they need a flexibility, they need the views without a steep learning curve. So it's really a win-win process. So I hear a lot of people say, I got a lot of sprawl, cluster sprawl. Let's get out of hand. Does that solve that? How do you guys solve that problem? Yeah, so the nested cluster is a perfect answer for that. So before using nested cluster, for a lot of enterprise to serving developers, they have to either create a very large, coordinated cluster and then isolated by namespace, which not ideal for a lot of situations because namespace is not a hard isolation. And also a lot of global resource like CRD and Operator does not work in namespace. But the other way is you give each developer a separate Kubernetes cluster. But that very quickly become too costly because not every developer is working 24-7. And half of the time, your cluster is a city idle and that costs a lot of money. So using nested cluster, you will be able to basically do all these inside the hosting cluster, bring the efficiency there. That is huge. It saves a lot of time, reduces the steps it takes. So I take a minute, my last question to you is to explain, what's in it for the developer? If they work with Spectre Cloud, what is your value for, what's the pitch? Not the sales pitch, but like, what's the value pitch that you give them? Yeah, and the value for us is again, there are a number of different services and teams people are using today are so many. There are so many different languages, there are so many different libraries, there's so many different capabilities. It's too hard for developers to have to understand not only the internal development tools, but also the Kubernetes, the containers, the technologies, there's too much for it. Our value prop is making it really easy for them to get access to all these different integrations and tooling without having to learn it. And then being able to very easily say, I wanted to pull this into a cluster, again, whether it's a nested cluster or a host cluster, but the next layer on top of that is how do we also share those abilities with other teams? If I build my application profile, developing an application, I should be able to share with my team members with Tenri saying, hey Tenri, why don't you also take a look at my app profile and let's build and collaborate together on that. So it's about collaboration and be able to move really fast. I mean more developers got to be more productive. That's number one hit here, great job. Exactly, last question before we run out of time, is this GA now? Can folks get their hands on it, where? Yes, yeah, it is GA and available both as a sauce and also the oncoming storm. Awesome guys, thank you so much for joining us. Congratulations on the announcement and the momentum that Spectre Cloud is powering itself with. We appreciate your insights and your time. Thank you so much. Thank you for having us. For our guests and John Furrier, Lisa Martin here live in Michigan at KubeCon CloudNativeCon 22. Our next guests join us in just a minute, so stick around.