>>from around the globe. It's the Cube with digital coverage of VM World 2020 brought to you by VM Ware and its ecosystem >>partners. Hello and welcome to the Cube. Special coverage of VM World 2020 Virtual I'm John for host of the Cube were stupid men Day volonte all doing interviews covering the virtual version of VM World. First time it's ever happened. We've been covering VM World for over 10 years, our 11th season with Cube at VM World. And of course, it's difference virtual. But we're doing our part. We're getting in the programs. We need to get the stories out and we got a great guest here. Submit to on who's the chief customer officer of the M where, uh, back to VM, where he ran the end user computing of which we covered air. Watch a lot of great announcements Submit. Great to see you. Thanks for coming on to the Q. Virtual >>John. Great to see you again. And great to be back on the Cube. >>So great to see you. And again I know you. You came in your back into the wheelhouse of VM ware. But as the theme of this show is putting the digital foundation for an unpredictable world. Also, with Covidien going virtual makes a lot of sense. However, VM Ware has been doing extremely well on the business performance side and making all the right tech moves we've been covering them to Cuba is well documented, the business models evolving. The performance is there. You are in a new role for VM, where its newly created chief customer officer tell us why you're back. Why this role? Why is it important? >>Yeah, great question, John. You know, I I joined the anywhere because we end where I look at sort of what bm where is trying to do all aligned with what customers want If you think about customers, they have been up until now, dabbling with cloud building sort of strategies on how to embrace Cloud, which applications will go to which parts off the cloud. And it has been something that has been more off slow RL strategy and with the multi cloud transition plan. Now, VM Ware provides to some extent this, you know, started out with operating system for the hardware, and it has evolved to provide operating system for the cloud it truly runs applications across multiple clouds. And with our partnerships with AWS Azure, Microsoft Google, we're able to sort of give our customers this multi cloud platform for them to run any application, whether that's traditional or modern, in a sort of unified operational fashion. Now this is a different subscription world for customers, right and customers in the world of cloud, especially when they're going into this kind of a transformational journey. Um, you know, it requires we anywhere to think slightly differently. It's not just the traditional cell implement support kind of customer model. You have really help them achieve their out, come over a period of time and then make them successful as they continue to sort of face the uncertainties off the multi cloud world. So So So Pat and Sanjay decided to create this new customer experience office and all different functions from success support digital engagement as well a czar insulting professional services. Tam's were put together so that we can offer integrated experiences to the customer. And that sounded exciting and, you know, we're making tons off interesting innovations there. Some announced that GM World and, uh, very much aligned with an objective to help our customers. >>E. I want to dig into the news and the announcement because I think there's a specific thing I'd like to drill into. But I want to get your thoughts submit because I think VM Ware and I thought to Sanjay about this as well as Pat. Clearly. Cooper Days is the dial tone of the Internet investment cloud Native Project. Monterey speaks to Multi cloud, totally get it. But Cove it has accelerated not only VM where every company, whether they're on the delivery side of it selling side or even consuming of the technology cloud, for instance, has forced the digital transformation. And it's catching some people off guard, right? So what are your thoughts? Because, you know, you have a value projects, you sell it to customers, you implement it, you support it. I mean, that >>was a >>nice grew swing for enterprise vendors like VM Ware. But now, with cove, it and all the digital transformation acceleration, it's causing a lot of people to be ready faster. How >>do you get >>that readiness? What do you bring to the table? What's your view on this? What's your reaction? Because people >>try to >>figure this out. It's confusing. >>I mean, I You know what it's it's very interesting. For example, I will give you an example. There's like, two extremes, and both of them are dealing with a very similar situation, all caused because of prove it. Okay, On one end of the spectrum, there are customers who are saying, Listen, our business is doing extremely well because of digital, and all of a sudden, uh, business needs this rapid agility, which can only be achieved through modern applications, and they're able to sort of move these applications because of elasticity of the cloud and leveraging multiple clouds. To do so is extremely important. If you're on one side of the spectrum on your business, where the business is doing extremely well, you have a percentage of the business that was coming from e commerce. All of a sudden that e commerce has accelerated. You know you can think off certain retailers, you know. Large scale retailers in that segment, and their their multi cloud journeys are accelerated, mostly because off just this surge in demand and change in capabilities that are needed to perform digital engagement with customers at a much much rapid pace, which are very difficult to do without leveraging multiple clouds. That's one extreme. The other extreme is, you know, I'll give you an example from large scale airlines and we all know in the travel hospitality airline business, this is extremely slow business for them, right at this point of time, and they're using the opportunity off this sort of time when things are slower to say, Okay, why don't we take this opportunity to fundamentally change our distilling it and truly embraced multi cloud while doing so? Because there is an opportunity to do so. The workload on the application than the infrastructure does not high little more technology reasons. A little bit more sort of a for downtime reason sort of go through the transformation faster. In other words, both ends of the spectrum. I'm seeing customers move the words sort of this destination fast it. And guess what? There is really no one at this stage outside of VM ware who can help them achieve that because otherwise you set a single voice. You know, there are their players who died. You tow their singular cloud solution and running. You know what I what I tell customers is multi cloud doesn't mean you are running two different architectures on two different clouds, right? That's not multi cloud. Multi cloud means running a singular architectures on multiple clouds, because that's when you get through governance and true operational scale and true experience and elasticity and control. And that's what we, um, where is all about? So we are now engaged with those conversations and helping customers at both the front end right when they're engaged with us at this stage. But we have also down tailored our service delivery and our success off offerings and are how we engage with customers digitally and sort of technically and through people. Uh, in once they start their journey with us, Um, and they sort of embark on leveraging the technology into multi cloud I want. So So that's the sort of shift that has occurred. >>Yeah, I want to unpack the offering in a second, but I want to stay in the customer experience for a minute. We've heard that cliche a customer experience. So digital transmission. Okay, it's actually happening now, and I totally agree with you, by the way there's there's the modernization trend. You just basically spoke to the spectrums. But it's about modernization. Okay, if you think modernization, you think business model business model is Hey, it's pretty light right now. I'm not a lot of people traveling. Let's retool, Let's modernize, Let's use our resource is and modernize our business, which is a lot of applications. It's everything up and down the stack. And then the companies that have a tailwind with Covic, who have had the epiphany and saying, If we don't building modern app or have modern APS in market, we're out of business. So there's a critical urgency to, uh, coming out of it with a growth strategy that's a business model transformation. Totally get that. That's where the customers are. So the question for you is okay. How do you talk to the customer that is saying, Hey, I'm building a modern app. We have to pivot, were forced to pivot whatever word you want to use force to survive. They're now they have to build a modern app. How do you guys support that customer? How does that customer? What does that customer need to be successful? >>Yeah, I mean, I think it starts with an architectural approach right. We bring to the customers and architectural approach across multiple clouds that helped them when they go for their existing applications or new modern applications conforming toe, one operating model and one architectures. Because in this in this time, you know, customers have many critical line of business applications. This airline customer I was talking about, they have 600 applications that are quite critical. They sort of segment them out on which one they will truly modernize because of the business model modernization like you mentioned and which ones they will live with, the way they are for multiple reasons and how it starts with connecting them with a unified architect chair and a unified operating model is how we start with customers. Okay. And that is where the power off the younger comes in. Because, like I said, it becomes this architectural operating system for for the customers to run and adopt multiple clouds. >>You gotta be the chief customer officer. You're the quarterback. You're the one in charge of making sure customers were happy. Okay? And they get what they need. And again, there's different aspects of it. What do you guys announcing it? VM World 2020 virtual, um, that people should pay attention thio around servicing customers in this new subscription and SAS world. >>Yeah, I think besides the technology announcements in terms off modern, sort off, multi cloud platform, the architectural with Project Monterey from the customer experience side, we did announcement to announcements. One was for customers embarking on a journey. We want to make sure that customers get everything they need to be successful on the journey on an ongoing basis. Some off these journeys for large customers, John can take not just sort of three months, but three years because they're dealing with various applications. So for that we announced two pretty simple and easy to embrace offerings. One is AP navigator. AP Navigator enables customers to quickly assess which applications I have to be, you know, on one end, you know, rewritten, completely rewritten and on the other end simply sort of re hosted. Okay, and there are multiple options in between, and we call them as a five, our model with customers, and we guide customers through our own assessment and working with customers on how to sort of segment their applications and use a common architectures across all of them that we can then help and it and secondly, toe help them with. We announced something called Success 3 60 Success 3 60 is Our Mechanism Toe guide and help customers on an ongoing basis for a success plan with continuous, sort off adoption guidance designed workshops as well as providing they're dedicated support that customers need for embracing multiple cloud across all the cloud. With this architectural this way, customers get assured that they're able to get the right up front sort of assessment on applications and ongoing success. Okay, And that's sort of what we announced within customer experience side. And we have been able all of this available two people you know there are critical for large scale engagements, but also digital, you know, just like our customers are innovating with digital. We innovated with our own digital environment, and we brought it all together with something called customer Connect, all available with one single digital experience that's mobile friendly, alert driven, search driven. You know, all the AI that's needed at this point of time in terms of engaging with customers with proactive notifications and guidance in terms of how they're doing with success built into a singular experience so that they can engage with us, and we can engage with them to make them successful. >>And so it's people in technology you guys are bringing to the table. What can customers expect? Because, you know, as they've worked with the M where you've always had great technical support outside its have been a technology driven company. Um, but as you start getting into SAS, you're starting to get into the business model transformation. How do you guys impacting the customers and how you go to market and how you, uh, service your customer base? >>Yeah, I think there are two elements What customers can expect one. They don't have to stand up and engagement and experience mortal completely separate for a small set of applications on a completely different you know, cloud architectures. They could just fit and build a single experience off dealing with the M, where, as a mechanism to enable all of their applications to be hosted, regardless of which cloud there in Uh huh Sandvik they do it at their own pace, right? As then when they're ready for applications. Secondly, and more importantly, for the business model transformation side. We have a model where we continue to show them the value realization. Okay, because these are true business model transformations. At this stage, there is lot off investment that's coming into I P while at the same time, the rest off the business is doing belt type. So there is a continuous pressure on Earth. Customers are I t. That is the champion for the customers, and they're working with developers in line of business teams, and they have to continue to show how what they're investing into as a singular platform or in architecture is going to deliver some kind of a value on an ongoing basis. So we have delivered on an ongoing basis rip boards and feed back and continuous sort of information back to the customers so that they can take back to their businesses on all the investments they're making now are ongoing basis what value the business is getting, because at the end of the day in this, this is probably the first time in the where I I t is probably getting the least belt tightening in the case off sort of an economic downturn, and in fact, it is being looked at as a way to invest out off the downturn. Right? So they're going to be, in a way where there sometimes even going into the boardroom and showing not just governance, but also sort of the investments they made, what kind of value they they got. So those are the two things were providing seamless and at at pace move toe multi cloud with a common experience and second, ongoing value realization that they can communicate whoever they need. Toe >>submit. You know, we've been following VM where for many me personally of persons that was founded. But with the Cube since 2010 star 11th year, You know, we've been critical of times and pointing out the obvious and in some cases, not so obvious successes and challenges. Um and so we've seen the completeness of vision evolved and pat, certainly. You know, he he held the line and he did the right things. And then he executed. So, you know, as you look at the emerald, we're now been complimentary on some of the moves. Certainly on the technology side that you guys have made and then we again we've talked about this many times on the Cube. So complete in this, uh, vision check. Okay, this is wholesome. Michael Dell issues, but gave talks about that. So good vision complete executed business performance is there. But as you talk about sass and subscription, your ability to execute is going to be a key variable and things like the Gartner Magic quadrant for the areas you're competing in. Multi cloud talk about how you guys just set up financially to support that personnel. What is your organization gonna do? Can you share your vision? How you going to be able to execute customers success programs as this uncertainty around multi cloud continues to become reality and things are changing. >>Yeah, I think a couple of things firstly, you know, to be absolutely candid, you know, the pace at which the customers are going to the new multi cloud models is faster now than it was nine months ago. We just discussed that. Okay, so I wouldn't I would be misrepresenting if I said we always were ready for this kind of the case. We're also adjusting and innovating at this stage as fast as possible. The good news is that we were headed in the right direction. Okay, if we were headed in the wrong direction, it would have been much, much harder. Okay. Secondly, I think there is a very strong leadership, the leadership team. I mean, at the end of the day, it's vision, leadership, team investment, the components and, of course, diligence to execute that comes in for the execution. To me vision and the direction was always very, very strong. It motivated me to join the anywhere for this important mission. Second and many other exact. If second the leadership team is as strong as they get, the four team is extremely strong. We have strong leadership team leadership from Pat Michael, of course, as well as Sanjay Rgu Rajiv. Everyone provides strong leadership and then third, you asked about sort of the financial element. You know, they're The company continues to perform quite well, right? We have core businesses that some critical for customers to use as technologies to enable them, you know, to come out off this sort off economic issue we're facing and they're facing. So as a result, you know, financially, we're in a good position to be able to invest back into the business and Secondly, we have made now we've always, always been extremely strong on the technology front. Okay, now with Sanjay and packed sort of saying that we're going to be extremely strong in terms of customer experience front because the world of subscription, the world of cloud, the world off the SAS requires not just great technology but also a great customer experience. So we're seeing tremendous in a continued sort of support financially in terms of investing into the customer experience, from both getting the right set of people offerings as well as technology. So I believe we have all three things. Having said that, you know, some of these things that we're investing in. They need a lot of work, and I'm. While I'm proud of what we have accomplished, I truly believe you know the best is yet to come, and the right investments that we're making are going to continue to sort of enhance our offerings both through people as well as technology. But there's work to be done. You >>know, it's all about, you know, having the consume ability of the technology thio, the value proposition of VM ware and also also is a company being um, open and easy to work with and consumable that way. So I think this is a great time. Certainly. Product wise. Business wise, You guys do extremely well. Congratulations on your new role on the senior leadership is the chief customer officer of VM Ware will be following the stories of your customers. So I really appreciate you taking the time. >>Thank you. Thank you so much, John. Excited to be back. Great >>to have you back on the queue here. VM world coverage of 2020 virtual. I'm John for this. The host of Cube Virtual. Check us out cube dot Net. And also our new cube 3 65 where it's our new modern application for virtual events. Of course, we want to continue to tell the most important stories and cover all the key people making it happen. Submit. Thank you for coming on. This is the Cube. Thanks for watching

>>this session will be reviewing the power benefits of implementing a secure software supply chain and how we can gain a cloud like experience with flexibility, speed and security off modern software delivery. Hi, I'm Matt Bentley, and I run our technical pre sales team here. Um Iran. Tous I spent the last six years working with customers on their container ization journey. One thing almost every one of my customers is focused on how they can leverage the speed and agility benefits of contain arising their applications while continuing to apply the same security controls. One of the most important things to remember is that we are all doing this for one reason, and that is for our applications. So now let's take a look at how we could provide flexibility all layers of the stack from the infrastructure on up to the application layer. When building a secure supply chain for container focus platforms, I generally see two different mindsets in terms of where the responsibilities lie between the developers of the applications and the operations teams who run the middleware platforms. Most organizations are looking to build a secure yet robust service that fits the organization's goals around how modern applications are built and delivered. Yeah. First, let's take a look at the developer or application team approach. This approach follows Mawr of the Dev ops philosophy, where a developer and application teams are the owners of their applications. From the development through their life cycle, all the way to production. I would refer this more of a self service model of application, delivery and promotion when deployed to a container platform. This is fairly common organizations where full stack responsibilities have been delegated to the application teams, even in organizations were full stack ownership doesn't exist. I see the self service application deployment model work very well in lab development or non production environments. This allows teams to experiment with newer technologies, which is one of the most effective benefits of utilizing containers and other organizations. There's a strong separation between responsibilities for developers and I T operations. This is often do the complex nature of controlled processes related to the compliance and regulatory needs. Developers are responsible for their application development. This can either include doctorate the development layer or b'more traditional throw it over the wall approach to application development. There's also quite a common experience around building a center of excellence with this approach, where we can take container platforms and be delivered as a service to other consumers inside of the I T organization. This is fairly prescriptive, in the manner of which application teams would consume it. When examining the two approaches, there are pros and cons to each process. Controls and appliance are often seen as inhibitors to speak. Self service creation, starting with the infrastructure layer, leads to inconsistency, security and control concerns, which leads to compliance issues. While self service is great without visibility into the utilization and optimization of those environments, it continues the cycles of inefficient resource utilization and the true infrastructure is a code. Experience requires Dev ops related coding skills that teams often have in pockets but maybe aren't ingrained in the company culture. Luckily for us, there is a middle ground for all of this Doc Enterprise Container Cloud provides the foundation for the cloud like experience on any infrastructure without all of the out of the box security and controls that are professional services Team and your operations team spend their time designing and implementing. This removes much of the additional work and worry Run, ensuring that your clusters and experiences are consistent while maintaining the ideal self service model, no matter if it is a full stack ownership or easing the needs of I T operations. We're also bringing the most natural kubernetes experience today with winds to allow for multi cluster visibility that is both developer and operator friendly. Let's provides immediate feedback for the health of your applications. Observe ability for your clusters. Fast context, switching between environments and allowing you to choose the best in tool for the task at hand. Whether is three graphical user interface or command line interface driven. Combining the cloud like experience with the efficiencies of a secure supply chain that meet your needs brings you the best of both worlds. You get Dave off speed with all the security controls to meet the regulations your business lives by. We're talking about more frequent deployments. Faster time to recover from application issues and better code quality, as you can see from our clusters we have worked with were able to tie these processes back to real cost savings, riel efficiency and faster adoption. This all adds up to delivering business value to end users in the overall perceived value. Now let's look at see how we're able to actually build a secure supply chain. Help deliver these sorts of initiatives in our example. Secure Supply chain. We're utilizing doctor desktop to help with consistency of developer experience. Get hub for our source Control Jenkins for a C A C D. Tooling the doctor trusted registry for our secure container registry in the universal control playing to provide us with our secure container run time with kubernetes and swarm. Providing a consistent experience no matter where are clusters are deployed. You work with our teams of developers and operators to design a system that provides a fast, consistent and secure experience for my developers that works for any application. Brownfield or Greenfield monolith or micro service on boarding teams could be simplified with integrations into enterprise authentication services. Calls to get help repositories. Jenkins Access and Jobs, Universal Control Plan and Dr Trusted registry teams and organizations. Cooper down his name space with access control, creating doctor trusted registry named spaces with access control, image scanning and promotion policies. So now let's take a look and see what it looks like from the C I c D process, including Jenkins. So let's start with Dr Desktop from the doctor desktop standpoint, what should be utilizing visual studio code and Dr Desktop to provide a consistent developer experience. So no matter if we have one developer or 100 we're gonna be able to walk through the consistent process through docker container utilization at the development layer. Once we've made our changes to our code will be able to check those into our source code repository in this case, abusing Get up. Then, when Jenkins picks up, it will check out that code from our source code repository, build our doctor containers, test the application that will build the image, and then it will take the image and push it toward doctor trusted registry. From there, we can scan the image and then make sure it doesn't have any vulnerabilities. Then we consign them. So once we signed our images, we've deployed our application to Dev. We can actually test their application deployed in our real environment. Jenkins will then test the deployed application, and if all tests show that is good, will promote the r R Dr and Mr Production. So now let's look at the process, beginning from the developer interaction. First of all, let's take a look at our application as is deployed today. Here, we can see that we have a change that we want to make on our application. So marketing Team says we need to change containerized injure next to something more Miranda's branded. So let's take a look at visual studio coat, which will be using for I D to change our application. So here's our application. We have our code loaded, and we're gonna be able to use Dr Desktop on our local environment with our doctor desktop plug in for visual studio code to be able to build our application inside of doctor without needing to run any command line. Specific tools here is our code will be able to interact with docker, make our changes, see it >>live and be able to quickly see if our changes actually made the impact that we're expecting our application. Let's find our updated tiles for application and let's go and change that to our Miranda sized into next. Instead of containerized in genetics, so will change in the title and on the front page of the application, so that we save. That changed our application. We can actually take a look at our code here in V s code. >>And as simple as this, we can right click on the docker file and build our application. We give it a name for our Docker image and V s code will take care of the automatic building of our application. So now we have a docker image that has everything we need in our application inside of that image. So here we can actually just right click on the image tag that we just created and do run this winter, actively run the container for us and then what's our containers running? We could just right click and open it up in a browser. So here we can see the change to our application as it exists live. So once we can actually verify that our applications working as expected, weaken, stop our container. And then from here, we can actually make that change live by pushing it to our source code repository. So here we're going to go ahead and make a commit message to say that we updated to our Mantis branding. We will commit that change and then we'll push it to our source code repository again. In this case we're using get Hub to be able to use our source code repository. So here in V s code will have that pushed here to our source code repository. And then we'll move on to our next environment, which is Jenkins. Jenkins is gonna be picking up those changes for our application, and it checked it out from our source code repository. So get Hub Notifies Jenkins. That there is a change checks out. The code builds our doctor image using the doctor file. So we're getting a consistent experience between the local development environment on our desktop and then and Jenkins or actually building our application, doing our tests, pushing in toward doctor trusted registry, scanning it and signing our image. And our doctor trusted registry, then 2.4 development environment. >>So let's actually take a look at that development environment as it's been deployed. So here we can see that our title has been updated on our application so we can verify that looks good and development. If we jump back here to Jenkins, will see that Jenkins go >>ahead and runs our integration tests for a development environment. Everything worked as expected, so it promoted that image for production repository and our doctor trusted registry. Where then we're going to also sign that image. So we're signing that. Yes, we have signed off that has made it through our integration tests, and it's deployed to production. So here in Jenkins, we could take a look at our deployed production environment where our application is live in production. We've made a change automated and very secure manner. >>So now let's take a look at our doctor trusted registry where we can see our game Space for application are simple in genetics repository. From here we will be able to see information about our application image that we've pushed into the registry, such as Thean Midge signature when it was pushed by who and then we'll also be able to see the scan results of our image. In this case, we can actually see that there are vulnerabilities for our image and we'll actually take a look at that. Dr Trusted registry does binary level scanning, so we get detailed information about our individual image layers. From here, these image layers give us details about where the vulnerabilities were located and what those vulnerabilities actually are. So if we click on the vulnerability, we can see specific information about that vulnerability to give us details around the severity and more information about what, exactly is vulnerable inside of our container. One of the challenges that you often face around vulnerabilities is how, exactly we would remediate that and secure supply chain. So let's take a look at that and the example that we were looking at the vulnerability is actually in the base layer of our image. In order to pull in a new base layer of our image, we need to actually find the source of that and updated. One of the ways that we can help secure that is a part of the supply chain is to actually take a look at where we get our base layers of our images. Dr. Help really >>provides a great source of content to start from, but opening up docker help within your organization opens up all sorts of security concerns around the origins of that content. Not all images are made equal when it comes to the security of those images. The official images from Docker, However, curated by docker, open source projects and other vendors, one of the most important use cases is around how you get base images into your environment. It is much easier to consume the base operating system layer images than building your own and also trying to maintain them instead of just blindly trusting the content from doctor. How we could take a set >>of content that we find useful, such as those base image layers or content from vendors, and pull that into our own Dr trusted registry using our rearing feature. Once the images have been mirrored into a staging area of our DACA trusted registry, we can then scan them to ensure that the images meet our security requirements and then, based off the scan result, promote the image toe a public repository where we can actually sign the images and make them available to our internal consumers to meet their needs. This allows us to provide a set of curated content that we know a secure and controlled within our environment. So from here we confined our updated doctor image in our doctor trust registry, where we can see that the vulnerabilities have been resolved from a developers point of view, that's about a smooth process gets. Now let's take a look at how we could provide that secure content for developers and our own Dr Trusted registry. So in this case, we're taking a look at our Alpine image that we've mirrored into our doctor trusted registry. Here we're looking at the staging area where the images get temporarily pulled because we have to pull them in order to actually be able to scan them. So here we set up nearing and we can quickly turn it on by making active. Then we can see that our image mirroring will pull our content from Dr Hub and then make it available in our doctor trusted registry in an automatic fashion. So from here, we can actually take a look at the promotions to be able to see how exactly we promote our images. In this case, we created a promotion policy within docker trusted registry that makes it so. That content gets promoted to a public repository for internal users to consume based off of the vulnerabilities that are found or not found inside of the docker image. So are actually users. How they would consume this content is by taking a look at the public to them official images that we've made available here again, Looking at our Alpine image, we can take a look at the tags that exist. We could see that we have our content that has been made available, so we've pulled in all sorts of content from Dr Hub. In this case, we have even pulled in the multi architectural images, which we can scan due to the binary level nature of our scanning solution. Now let's take a look at Len's. Lens provides capabilities to be able to give developers a quick, opinionated view that focuses around how they would want to view, manage and inspect applications to point to a Cooper Days cluster. Lindsay integrates natively out of the box with universal control playing clam bundles so you're automatically generated. Tell certificates from UCP. Just work inside our organization. We want to give our developers the ability to see their applications and a very easy to view manner. So in this case, let's actually filter down to the application that we just deployed to our development environment. Here we can see the pot for application and we click on that. We get instant, detailed feedback about the components and information that this pot is utilizing. We can also see here in Linz that it gives us the ability to quickly switch context between different clusters that we have access to. With that, we also have capabilities to be able to quickly deploy other types of components. One of those is helm charts. Helm charts are a great way to package of applications, especially those that may be more complex to make it much simpler to be able to consume inversion our applications. In this case, let's take a look at the application that we just built and deployed. This case are simple in genetics. Application has been bundled up as a helm chart and has made available through lens here. We can just click on that description of our application to be able to see more information about the helm chart so we can publish whatever information may be relevant about our application, and through one click, we can install our helm chart here. It will show us the actual details of the home charts. So before we install it, we can actually look at those individual components. So in this case, we could see that's created ingress rule. And then it's well, tell kubernetes how to create the specific components of our application. We just have to pick a name space to to employ it, too. And in this case, we're actually going to do a quick test here because in this case, we're trying to deploy the application from Dr Hub in our universal Control plane. We've turned on Dr Content Trust Policy Enforcement. So this is actually gonna fail to deploy because we're trying to deploy application from Dr Hub. The image hasn't been properly signed in our environment. So the doctor can to trust policy enforcement prevents us from deploying our doctor image from Dr Hub. In this case, we have to go through our approved process through our secure supply chain to be able to ensure that we know our image came from, and that meets our quality standards. So if we comment out the doctor Hub repository and comment in our doctor trusted registry repository and click install, it will then install the helm chart with our doctor image being pulled from our GTR, which then has a proper signature, we can see that our application has been successfully deployed through our home chart releases view. From here, we can see that simple in genetics application, and in this case we'll get details around the actual deploy and help chart. The nice thing is that Linds provides us this capability here with home. To be able to see all the components that make up our application from this view is giving us that single pane of glass into that specific application so that we know all the components that is created inside of kubernetes. There are specific details that can help us access the applications, such as that ingress world that we just talked about gives us the details of that. But it also gives us the resource is such as the service, the deployment in ingress that has been created within kubernetes to be able to actually have the application exist. So to recap, we've covered how we can offer all the benefits of a cloud like experience and offer flexibility around dev ups and operations controlled processes through the use of a secure supply chain, allowing our developers to spend more time developing and our operators mawr time designing systems that meet our security and compliance concerns