 Hello and welcome back to another OpenShift Commons. If you haven't heard, 4-8 is coming out soon and we had the PMs do a what's new in 4-8. So go back and watch that, but what we're doing now is a deep dive into all the different areas that are new in 4-8. So we're really excited today to have Serena with us, who is the PM for the developer experience of the OpenShift console. So she's going to do a deep dive into what's new in the developer console and OpenShift. And and from there, we'll get you started with other things that are new in OpenShift 4-8 as well. And Serena, do you want to introduce yourself more than I just did? And sure, yeah, my name's Serena Nichols and I'm a product manager in the developer tools for you, and I am specifically working on the develop experience in the OpenShift console and ODO. So thanks for having me here today. And I'm going to try to go back and forth between a deck and a demo. But as we know, usually when we do demos, oftentimes we'll make we might encounter some issues. So forgive me if that happens. So I wanted to kind of go through a number. Is it all right if I just kick it off, Serena? Just start. Exactly, that's perfect. OK, perfect. All right. So the first thing I wanted to just introduce is that we have had an ad page redesign, so I'm going to go into the ad page here. And to improve our onboarding, we have a new Getting Started Resources card, which is which is shown here for developers on the ad page. And it provides resources to create applications using samples. What you can see here. So we have a Corkus sample and a Spring Boot sample so people can get up and started quickly to start kicking the tires. We also have this area that allows you to build with guided documentation, which is referencing our Quick Starts, which we have started in 4.6 and continue to improve with each release. And then we also have the ability to kind of explore some new developer features. So we're showing that there's certified Helm charts and as well as having a link to some new resources. And you're going to forgive me because I am on a development cluster. So this is saying 4.9 because I've got a little bit of 4.9 inside of my console that I'm running on right now. So you'll see what's new in OpenShift 4.8. Obviously, when you have 4.8 installed and that links off to the latest and greatest blog explaining the newest features. You also have the ability to kind of hide this from your view if you want. So if that's something that you don't want to see, you can do that. And you can also turn these details on and off. So it's just a redesign of that page. And that's kind of what we have there. So the next item that we're going to show is we'll talk about that we do have new samples available. So if I go back to the ad page and hit this samples item here, we'll see that we've always had this kind of samples catalog, but it used to be predominantly powered by builder images. We now also have this powered by dev files, which are new. And so, for example, we do have a corkis sample here that's available. So I can quickly import a dev file, which is a corkis app and just hit create. So again, just a way to quickly and easily get a corkis app started and deployed into OpenShift to be able to kick the tires with that. If you want to learn more about dev files, there is a dev file.io site that you should be able to find the latest and greatest information about that. In addition, we also have a dev file catalog. So if you go to our developer catalog today, we've got a number of different sub catalogs in here. We have builder images, dev files, event sources, home charts, operator back services and templates. So as I click on dev files, you'll see the four dev files that we do have available here today. These are continuing to be created. So you'll see more and more come out through here. But right now we're starting with a basic set of four around Node.js, Python, corkis and Spring Boot. Please let me know if there's any questions along the way and just jump in, Karina, if there's anything that comes up. The next thing I wanted to show, let's see if we do. Okay, so we don't have on this cluster, I don't have the ability to show the home charts that are certified. But what I can do show here is just the mock-ups that we do have. So when we have home charts, we're using this icon. It's a blue badge with a white check in it. If that icon is shown, that means that it is a certified home chart. We also, so we now do have certified home charts coming through. And there's a link to home certification program announcement here as well, if you want to learn any more about that. In four, eight, the certified home charts are becoming available to developers from the catalog. Similarly to operators, that catalog is showing a badge for the certified charts. Those charts are also going to get visibility in the Red Hat Marketplace. And additional charts will be made available to the catalog. But if you're interested in some specific charts from partners, you can engage with partner teams, et cetera, for adding more certified charts. Okay. The next piece that we have done is allowed the ability to import a multi-dock YAML. So a highly requested feature, which was popular with the CLI users, is finally coming to the console. Users can now import multiple YAML files in one go or separate YAML files with dash, dash, dash delimiter and drag and drop that into the console. So I'm going to do an import YAML. And I am now going to drag and drop a YAML file. You can see me dropping it here. And as I drop that file, you'll see I have three different areas delimited by the dash, the three dashes. When I hit create, which is something that's very cool, is that it will show me all of the resources that were actually created now. So it gives me the status for all of those, which is very cool. And what that actually did was it created three console links that are just here immediately under the user menu. But this is going to be really nice for people instead of having to import files one at a time. They can either drag them in individually, I mean, all at once or have them in a single file to create multiple resources. And the best part, too, is that you also get the status of all that information. As I continue on, I'm going to talk about easy import for application artifacts. So this is the cool thing. We actually did focus this on at the April Summit demo, where we do a drag and drop capability. So if I am in topology and I'm going to create a brand new project, I can spell. You can see what happens is I'm just like in a topology area and it just says I can start building my application or visit the ad page for more details. What I can also do is I do have a jar file, which you probably can't see because I'm just sharing a single browser tab. But I am now dragging and dropping this jar file into or onto my topology view. And when I drop that, it brings up a form that says, do you want to upload your jar file? It gives a whole bunch of defaults for me. I can provide a lot more information if I'd like. I'm actually not going to deploy. I'm going to deploy this, but I'm not going to give all the I'm not going to run the application. So I'm just going to hit create by default right now. What you'll see is a jar file uploading alert notification and tells me that I can access the build logs if I want to. I can kind of go over there, check out what's going on. It does take a little bit because it is uploading that jar file, and then it's going to do a build. But it's a really quick and easy way for somebody to actually come in and take a local jar file that they've been developing on their local desktop and be able to deploy it into OpenShift by just drag and drop. So this is something that we're pretty excited about. And I've talked about, you know, how do we bring this forward going forward? Do we want to do the same thing with HomeChart archives, et cetera? So it's a nice new feature for Doves to get up and running really quickly. And we can see that that build is continuing to run. So I'm just going to I'm going to continue to go to the next piece to demo. The next one is around improved search in our catalog and in our topology. So I'm just trying to call out where these areas are in the different views. So if I go to the topology view, there is an icon here. We added this feature a couple of releases ago. I think we added it in 4.6, but not everybody's aware of it. So I'm going to demo this again just really quickly. If I click on that, what it does is it allows me to do a quick search of not only the developer catalog, but the sample catalog and the quick start catalog. So what we've done here to improve the search capability is that rather than searching for an entire string, we're kind of matching substrings. So if I wanted to type in corkis, I can see, okay, I've got four matches for corkis, but if I just want to see a corkis quick start, I can start typing that. So it's actually taking matches from the description, from a tile, as well as that sub-catalog type, which is nice. That was something that we weren't able to do previously and I'll give you another example. So this is the one I always used to do is postgres and then ephemeral. Now that they're doing like two substring matches, you're able to easily put two different items together and able to see that powerful search match. So we have that capability here inside of the topology search, but we also have it inside of our developer catalog. If I go back over here and press and then ephemeral, we see that that also works the same way in the developer catalog. So again, just a more powerful search that will hopefully allow users to find things much faster than they had previously. The next piece is another one of our items, which is parity with 3.x. So I think a lot of people who have been users of OpenShift through the 3.x timeframe, we did have quite a few form-based experiences in 3.x, which we have not completely finished providing parity for in 4.x. So the good news is in 4.8, we will have a form-based edit for deployments and deployment configs. So if I go back into my topology view and let me just go, I think I have one in here, I do. So I can click on this deployment and you can see either in my actions menu here, I have an edit deployment or I could do a right click, which brings up edit deployment. And this brings me to a form, which is awesome. So this would be enable me to quickly come down here, change any of the basic options for deployment strategy, et cetera, but also lets me access some of those advanced options like pause, rollouts and scaling. So it allows me to do this through my form view instead of doing YAML view. And of course, if people do prefer YAML editing, they can still go over to the YAML view and do that, but our default is the form view. I know that was a frequently asked request from customers, so that should definitely make a lot of people happy who are coming over from 3.x. Okay, the next item that I was gonna go over is around expanded UI for serverless. So when the serverless operator is installed, we continue to enhance the console and we've made progress in three main areas. The first one is that we have provided a new tech preview command, which is called make serverless and it creates a new serverless deployment next to your existing deployment. Other configurations, including the traffic pattern can also be modified in the form. So what I'm gonna do here is this, and this is around, oops, I'm sorry, this is again around the ability to take an existing application and convert it to serverless. Now the reason we're calling it tech preview is because at this moment, it was our first round of this capability, but also right now what we're doing is we're just leaving that initial deployment. So if I click on on that deployment, like I've showed before, you can either get it to the actions menu on the right-hand side or you can get it through right click here. If I click on make serverless, it brings up a form, note it does show tech preview. It gives me all kinds of information and defaults that are provided and then also does allow me to do some additional advanced options. I'm gonna take everything as the default here and I'm gonna hit create. And what you'll see is that KeyNative service is being created in that same application as my initial deployment was. This thing is still now running, the build is complete, there we go and the revision has now shown up. So I should hypothetically, if I click on this route, I should also be able to access the serverless application from here. Yeah, so it's available and ready. So it's a really nice tool to start migrating your regular applications and trying to see what that would look like if it was deployed as a serverless application. I'm gonna go on to the next item, which is around still sticking with the serverless. We do now have cloud function support in topology. So I'm gonna go back into the topology view and go into, sorry, I just have to find correct projects, there we go. So just to give an example of what things look like, this item here on the right-hand side is a KeyNative service. So as you can see, the logo on the bottom left-hand side is the KeyNative logo. You'll see that KSVC, that's indicating that it's a type KeyNative service. And what we do is we have a bounding box around all of the revisions that are in the active traffic block. So in this case, this KeyNative service has a single revision, 100% of the traffic is coming here. What we're doing for our cloud functions is something very similar. Interesting, looks like I just hit a little bug there with that tooltip, sorry about that. So but what we see here is this bounding box, if it's a cloud function, the bounding box has a purple, light purple or lavender background, but this really is a KeyNative service underneath. So we still have that resource badge that says KSVC, but what we're showing is a badge for showing that it's a cloud function. So that's the way to differentiate between a cloud function and a KeyNative service. The other kind of cool thing that we do have is we do have the ability to provide, I'm sorry, a cloud function can be a sync of an event source. So as I hovered over there, I saw a blue arrow that I'm just gonna kind of drag and drop onto the canvas. As I do that, I see that I have an event source option that's available. So I'm gonna click on event source and I'm going to choose the pink source here. What this allows me to do is create an event source that will kind of, here's the data that would go, that's gonna get posted to the target function. I'm gonna have this run, I think it's every minute. By default, it's already providing a sync to that event display function and I'll hit create. And what we should see is every minute, we'll see this cloud function kind of wake up from the pink source, there we go. And if we go into the logs of this, we'll actually see the data coming in. So let's see if I can successfully get there. We'll click here, go to the log, there's the cloud event. And I'm not sure if I'm getting the right, maybe one of those spots where I'm not gonna get what I'm looking for, but we'll see. I think we should be getting, this is the data here. And if I don't get it this time, we might just move on to the next. We are seeing the cloud event showing and that it's associated with the pink source. There's the next invocation. So we are getting the information. Again, it's, although we can't create cloud functions inside of the developer console through the UI yet, anything that's created in the backend or if that exists inside of the project or if you utilize the CLI, we're able to visualize it. So good to go there. The next item is just around. We also did provide some additional scaling options for Knative Services. So again, if I go back into the topology view and let's just say I was going to deploy an image and I would say I'm gonna make this resource not a deployment, not a deployment config, but a Knative Service. As I do that, the advanced options update and if I go to scaling, what you'll see here and I'm gonna just increase the text here a little bit so it's a little easier for people to read. We do now have the ability to specify the concurrency utilization, which allows users to set the percentage of concurrent requests before scaling up. And then also the other new one is that we're supporting is the auto-scaled window, which again allows users to set the duration to look back for marking auto-scaling decisions. That service ends up getting scaled to zero if no requests are received in that time period. So two very useful scaling options that we've now made available for our serverless apps. Okay, now I'm gonna move to OpenShift Pipelines. I'm going to find a pipeline application. Let's see, I'm gonna have to do a search real quickly because I forget which project I had this in. So give me one second. I do a search for all the pipelines and said, okay, here we go. So here is, it was in my test. Okay, great. So I'm gonna go back into the developer console. I'm in my test and I'm gonna go into the Pipelines area. And what I'll see is that I do have, sorry, I have to go into my test. Here we go. Here we go. So I have a pipeline that's living here now and what we'll see with the Pipelines information is that we're now in along with 48, let's see, along with 48, OpenShift Pipelines 1.5 is gonna GA. So what we'll see here is in the console, we've introduced feature parity with Tecton within the Pipeline builder as well as other pipeline related flows. So I'm gonna show you some of the information around one expressions and finally tasks. So somebody was nice enough to provide a pipeline for me here which does show the one expressions and finally tasks. So this diamond shaped is representing a one expression. So right now I'm looking at the Pipeline definition, right? So there's no status associated with this. So this is showing that there's one expressions for each one of these tasks. And then this larger white area, rectangular area is representing the different finally tasks which are available or specified as part of this pipeline. If I just run this pipeline, what we'll see is it will bring me automatically to the Pipeline run and saying that it's executed. What we'll see here is the one expression that's currently being run is shown in the dark blue. So we'll see that create file, which is a task is now being run. And if I hover over that create file task, you'll see that the step called the right new stuff is there and being executed. And as we continue waiting here for a couple of minutes, we'll see a lot of these, the different tasks inside that Pipeline run being run and we'll see what happens. So for example, if it's gray, if that one expression, that diamond is gray, that means that the expression was not met. So that task will not be implemented, or I'm sorry, will not be run. If it's green, that means that the one expression was met and that that task was then executed. So you can see here, there were two one expressions that are actually three that are green. So three that were met and actually the tasks were executed and then there were a number that remained gray that were not met. So those tasks were not executed. So it's nice to see that we now do have feature parity with the Tecton CLI and that we have this capability now inside of Pipeline so that you can see the status when your Pipeline has either a one expression or a finally task. What I'm also gonna do is just go into the Pipeline Builder quickly. And if I hit create Pipeline, I can get there two ways, by the way, I can either go to the Pipelines area and hit create Pipeline or I could go to the add page and I could hit Pipelines here. I'm gonna reset my font because I enlarged it earlier. So I'm gonna hit Pipelines. I'm gonna go to Pipeline Builder area and you can see here now this is my Pipeline visualization and you can see I have the ability to add a finally task here immediately if I wanna do. I also have the ability to add a task just like we had previously. So I'm just going to add something if this is not gonna be a Pipeline, that makes sense but I just wanna be able to show you guys a couple of things. So as I add a task, we see that red exclamation point up on the top left hand corner which is referencing the fact that there is something missing for my task. So you can see here I need a source or I need an input workspaces available. So that's why that red exclamation point is showing but if I wanted to add a one expression this is where I would do that. I would be able to add that one expression here and then you can see that diamond shape is showing up. I'm not gonna add that information here but I just wanted to show how you could do it. The other thing is when you add a finally task this again is the same list of tasks you have available. It just means that anything that's in the finally task section will get run automatically regardless of the status of those previous tasks that are not in the finally task section. There might be something that you might use for cleanup or something like that in your Pipeline. And so those are the main areas in Pipeline and Pipeline Builder where we had, we had talked about both the when expressions and the finally tasks. This piece I don't, I'm not able to demo today but I did wanna just show you in our cluster today we do have, if the GitOps operator is installed we have an environments page. Oh, actually there we go. We do have one application which has kind of been bootstrapped by cam so that it shows up inside of our console. This is, right now I don't have the latest version of GitOps installed so what my screenshot that's inside of this stack is even is a little bit better where it shows not only will it show the application name as well as the Git repository but it will also show you how many environments that application is been deployed to. So in this case it just shows, I'm sorry it shows one and when I hover over the one it shows me that the dev environment is synced and that's in sync with the status that we're getting from Argo and it also shows you that last deployment. So again, this nice, this improved visualization will be available when we have GitOps 1.2 GA on OCP-48 or any flavor of OpenShift. And our environment, like as it says our environments view in the console provides insight into the app lifecycle. We do also have the ability to kind of drill into one of these applications and in 4.8 this remains unchanged but this is in 4.9 you're gonna see some additional improvements to this view as well but this is showing you, okay my application called AppTaxi is running on my dev environment. If I wanted to I could link out to Argo CD to get more information and be able to do some additional use cases but it's showing me that I have a single deployment called Taxi that we do have that application running there's a pod that's actually running there and in this case the commit details are not available but this whole page here you'll see some significant improvements in the 4.9 timeframe as well. So pipelines and GitOps in that entire kind of outer loop experience is an area where we're putting a lot of effort and improvements in the coming, we have that as well but we're gonna continue to do that in the upcoming year. Any questions out there yet, Karina? Just it's looking great. I mean, I'm also seeing a lot of things that I've been eagerly awaiting, right? And then pipelines serverless, yeah, this is awesome. Just keep going, this is great, thank you. Okay, great. I probably only have about another 10 minutes or so so I just checking because now what I'm gonna do is I'm gonna jump in from where we were just talking about how the developer can do everything and what they can access. Now I'm gonna talk about customizing the developer experience. So as an administrator, how you might want to customize the experience for your developers to make them more productive or more efficient, those type of things. So what you'll see here actually is kind of exciting in my opinion always is that these three have actually come from customer requirements or I'm sorry, customer feature requests. With each release, we try to put in new features with new technologies but we're also always trying to kind of guide that and juggle that along with some improvements and usability improvements as well as customer requests. So this is an exciting piece for me to be able to share back with customers and users who are trying to communicate with us what they want and showing that we are trying to give them some of that information as well. So this is talking about some of the new Quick Start features that we have. What I'm gonna do here is I think everybody does probably has some awareness of what Quick Starts are but for if you don't, I'm gonna go to the help menu on the masthead and click on the Quick Starts menu item. That shows me all of our Quick Starts that we have available inside of the console today. What's interesting about Quick Starts is they are customizable so any administrator or actually any operator can create their own Quick Starts and make them available to anybody using the platform. What's really nice and what we've heard from our customers is that one of the exciting pieces about this is that they can create their own Quick Starts to help jumpstart their own developers or their own development teams to provide them with some additional information on what their standards might be or their best practices might be, for example. We can see here, we have some here that are talking about like adding health checks to your sample applications and things like that but you could really as an admin or even a team, a development lead, right? You could want to create some Quick Starts to help kind of jumpstart or onboard some of your development team and it's a pretty easy process. We've got a bunch of samples that are available but what I really wanted to talk about today is that we do have a new type of support inside of our Quick Starts which is integrated with our web terminal operator. So again, for people, if you don't know about the web terminal operator, definitely check it out. If you're an admin in the operator hub, we do have this web terminal operator when that is installed, what you'll see is you'll see that the icon up here on the top, Masthead. When I click on that, it takes a second. It's gonna create a workspace for me so it is gonna takes a second to connect to my terminal for me. But once I do that, I do have the ability to utilize command lines as much as possible, as much as I want and it's inside of my web browser. So why is this a nice feature for developers? It's all enclosed in a single browser but not only that. If you happen to be in an environment where you're not allowed to install CLIs on your own machine, this gives you the ability to run the CLIs from inside of this command line terminal, right? So it's a really nice, if you're kind of locked down and don't have that capability of doing the installation on your own desktops, you have the ability to access them here. So it's nice. Now, if I go back to my Quick Start, what I wanted to show you guys was the fact that we do have the ability to now have Quick Starts have the ability to do a copy to a clipboard or more importantly to run in a web terminal. So in this case, what I'm gonna show you is just one of, this is a sample Quick Start and what this does is, it's just gonna create a project, right? So here's the CLI command, OC New Project Sample Test App, right? This is very simple but just for just showing the example, I can either copy it to my clipboard if I want or I can run it in the web terminal. If by chance you don't have the web terminal installed, you'll only be able to copy it to your clipboard. But since I have web terminal installed, if I click that play icon, as soon as I click that, you'll see that here we go. It's executed the command and if I now go back into OpenShift, I'm gonna go to my topology view and see if there's a project called sample test app. So yeah, here we go. There's a project called that, nothing's in it yet. So now in the next step, what they're talking about is they're gonna create a resource using this Git repo. So the next command will be to deploy an app, OC new app. Again, if I click this and say run in the web terminal, what we hope to see is a deployment show up inside of our topology view. Now we see the command is executed, perfect. We see the deployment is being created right now if we hover over that bottom left-hand decorator as we call it, we see that that build is running. So what we could, I'm gonna, I'm just gonna close this nav so we have a little bit more space. And if I click on this, I think we'll also see the side pan. Oh no, we're gonna go directly to the build details. Sorry, let me go back over here, I'm sorry. I'll click on the deployment itself and we will see that the build is running. So there's another panel here. So now, so just note on this, the furthest right-hand panel that we're seeing now is this is the quick start panel. This panel on the bottom is our command line terminal panel, and then we also have the side panel for topology. So if I wanted to go look at the logs of my build, I could either click here or I could have clicked directly there, but now our build is complete. So we should see our pod spinning up. If I hover over this, we'll see, yep, there's one's pod pending. And hopefully in a second that turns dark blue, great. But now what we notice is there's no route for this resource. So it's no easy way for me to run this deployment. So now I'm gonna go back over to my quick start and it says expose the route by clicking this. And as I do that, you'll see down here, the route is shown automatically in the side panel. And then we see on the top right-hand quadrant, we have our route decorator. And it shows that I can, it's indicating that if I click on that, I will open the URL for that app. And there we go, there's our application. So pretty cool. It does give you the ability to have a quick start that does directions or gives you instruction for both different use cases or user flows through the UI itself and or utilize something that even one, another example that this might be really helpful for is when the console might not support everything 100%, you might be able to do something through a CLI that is not available and a quick start could help with that capability. I'm gonna leave this quick start now and I am cube admin. So what I'm going to do now is I'm going to put my nav back, go into the search section and just go to the console quick starts because this is what powers all of our quick starts. They are CRs. And if I create a console quick start by default, they do provide a kind of a default quick start that's available. But what I'm going to do, let's see, I thought there were supposed to be, yeah. So I apologize, there are supposed to be some snippets here which there are in 48 for some reason, my cluster is not showing them. So let me just go back directly into the example. Sorry, I'm trying to remember what it was called. There it is, okay demo, there we go. This is the one that is showing the syntax for copy and paste. So in this case, if you wanted to show the copy or the execute pieces inside of the quick start, the syntax is just kind of right here. And I also have this in the deck that I'll show again. It's just pretty easy where you utilize the copy or the execute command. Once we do typically have the sidebar that has snippets and we will have a snippet that puts this information in there for you into your YAML file. So it's pretty easy. But I'm gonna switch back over to my deck, which shows what the format is for the copy as well as what the format is for the execute. And if you put the execute command in, like I mentioned, it will provide icons for both copy and execute. Okay, so let's go to the next one. The next piece is around the fact that there's more ways to customize the developer experience by hiding individual features from the ad page. So we just kind of mentioned earlier at the beginning of this that we do have this redesign kind of ad page here. And what we have heard from customers is sometimes they might not want all of these features available for their development team. So I'm going to try to do this and we'll see, hopefully I don't fail. What I'm gonna try to do is remove the from Dockerfile piece from the ad setup. So I'm gonna have to cheat over here and go look and see what I need to do. So I'm gonna go to my, let's see. I have to go over to search, find console. Really hoping I'm doing the right one. Go into cluster, go to YAML. I can view my sidebar. I can go down to the stack area and view details here. And now I think I went to my own one, seeing how many I was gonna do. One sec, search one here. Yes, this is the right one. Okay, so let's just go back there to make sure I explain. There are two console resources. We want the one that's the operator.openshift.io. So if I click on that and then go into that resource, go to the YAML file and I view the sidebar. The cool thing about this is it does allow me to see the spec. So if I click the view details of the spec, it shows me that there's customization available and I can view details of that customization. And this is showing me that I can modify the ad page and it even provides the ability if I drill in a little bit more, it tells me that I can provide disabled actions here. So let's see if I can do this. So, oops, I need to do customization ad page disabled action. So let's see. All right, the other neat thing about this is it does have snippets. So it's telling me that it does have ad page actions and I can insert a snippet. So let's see if I can get this to work properly. I can open this up and see YAML. Oh, but this is gonna give me every different. So what this is showing you is all of the different keywords that you need to hide the different pieces. So for one second, I'm just going to share and I move my screen over so I can type this. See again if this works underneath stuck, what I'm going to do is add customization. I'm really making myself nervous here. I'm gonna say ad page. I'm gonna say disabled actions colon. And then I'm going to say hyphen space import from Docker file. And I'm gonna copy this just in case for some reason I have to do a reload and hit save. Okay, now let's go back over to the ad page. Whoops, yeah, and do a refresh. It does take a couple seconds if I've done it, right? Then maybe I haven't. There we go, phew, successfully. So import from Docker file is now not available anymore on this cluster for anybody to have access to. So again, as we just kind of went through this, I go back over to the view side bar and look at the snippets for somebody who wants to kind of set the access to hide some of those items. That is where you could see it, right? So disables upload jar pipeline, operator back services there's a number of things here that you can disable. And now, oops, one more thing here is we've got one more way to customize the developer experience which has been added in for eight. So I'm gonna show you another kind of fun area inside of the developer perspective is when you go to a project, so I have my project selected I go to the project item in the nav area. I've got three tabs here, if I go to project access this is something that was added a number of releases ago based on some extensive collaborative work we were doing with one of our customers and they were like, oh, it would be really nice if for a developer, if they could just say I wanna share my project with somebody easily rather than having to go into the admin side and fool around with robot names, et cetera is there an easy way we could do that? So what we had initially done was we created this project access page. This allows you to add access super quickly but what we did was we initially just said you could either have admin, edit or view rights. Well, so good news is customers or people are using this which is awesome but now they wanted to have the ability to customize this list of roles. So if they have their own custom roles they wanna be able to update those here so that a developer will be able to utilize one of those custom roles that the admin is provided. So let's see if we can do this again I'm gonna go back right over to it's gonna it's by editing the same console resource. We'll see if I can do this right this time. I go find that console resource I go into cluster, I go to YAML, go to my sidebar and going to spec customization and I will see here, let's see, project access. So project access allows customizing the available list of cluster roles, you can view the details so that's gonna be the context I need to have now it's project access and then available cluster roles and if I look at snippets I think we also have some information here we do so available cluster roles and then you would just add whatever you want for your example. So let's see what did I have here registry admin so I'm gonna try that again here so we already have a single customization which was ad-paged gonna try to make this larger so it's a little easier for people to see but I'll ask my spot, there we go. And now let's see what I need to do here is project access, let's go back to my notes project access and then available cluster roles. Available cluster roles. And then I'm just gonna type in admin, edit view and registry admin, okay. And I'm gonna copy it just in case, it is saved so there I am, I reset my spacing and my magnification. Go back to the developer perspective, go back to my project, go back to project access. Let's hit refresh again, I think it's, if I think there is a little bit of a timer here it may be a minute. I see though that now these are lowercase so I'm pretty sure, yeah there we go. So now we do have registry admin is now available. So again, super easy way for an administrator by utilizing the Amel editor to kind of customize these couple of different areas inside of the developer experience. So this is pretty exciting stuff to make the devs life easier. So with that I know we probably still have about eight or nine minutes left but I did want to just kind of open it up if there's questions or comments also just so you guys do know there is a link on developers.redhat.com now that we do have a what's new link and that will point to the latest what's new blog for the latest release and that's gonna again be focused on the developer use cases and what's new and maybe point out to other blogs or other references as well. And also just gonna mention my Twitter handle is SerenaMarie125. If anybody ever has feedback, complaints, happiness any of that wants to connect on possible feature requests or you might see something wrong or any type of comment please feel free to reach out to me. Like I mentioned I'm a product manager on the dev experience side of the console and I'm always looking for any type of feedback. So with that I will pass back to Karina and see if we've got anything else to talk about. Thank you so much. I'm really excited about all the new features that you were able to get into 4.8 especially the CLI, the web console CLI. I think that's my favorite. Yeah. What is your favorite that you were able to get into 4.8 that the engineering teams were able to? Well, I think the most exciting one seemed to be the drag and drop for the jar file. It seemed to get a lot of excitement I think. So I think that was like, I don't know, it's a similarity YouTube of just being able to drag and drop things in and quickly deploy though for us, right? So that was awesome. I would say the other pieces that we did not talk about today is the managed Kafka capabilities. And unfortunately, I just didn't have the setup to show that but that's also an off large part of what we've been working on for the previous quarter. So there's a lot of excitement there around being able to have Red Hat manage Kafka and be able to utilize that from inside the console. And I apologize because my dogs just ran in. So if you hear noise in the background, that's not me. Well, we'll definitely have a talk on the managed Kafka service up coming soon as well. I'm really looking forward to that and getting people's feedback on that. That'll be great. We also have a number of other deep dives that are coming as well on this current release. So please stay tuned for that. I'll throw up the link. Yeah, there you go to all the upcoming ones as well. July is going to be fortune hot with new release updates. Yeah, they all look great. I'm especially excited for Mark Curry's, I don't know. I'm a huge fan of Mark and all his networking, everything he's able to get into OpenShift for networking. And of course, serverless, we had Nina on before talking about serverless functions. So that'll be a great update. And of course, pipeline. All right, I like them all. What can I say? Lots of good stuff going on for sure. We're all plug and biased. Yeah, exactly. I also want to give, can I give one more clip? Oh, be definitely. Okay, so in the near future, so we are moving towards dynamic plugins for our UI, which means an operator can provide their own UI to be installed when the operator is being installed. So right now what we do is any extensions we have to their console, they live in the console code base. The really cool thing about dynamic plugins is that once we have this available early part of next year, we're gonna have a pilot program for allowing customers to also, or other users to customize their own console. So, you know, stay tuned if those are things that you're interested in, stay tuned or connect with myself or Ali Lovram is the PM on the admin side who's we're both working on this. So it's a pretty exciting piece for both our operator story as well as for users. Thanks for that. Kudos on the terminal CLI feature also. Thanks, Shana. Great, and thank you so much for joining us and showing us everything that's new in the 4.8 console for developers. And again, reach out to Serena on Twitter. And she's quite active there. And thank you everyone. And be sure to join us for next time when we talk about pipelines. What's new in pipelines and GitOps and 4.8? So thank you everyone. And Chris, can you see us out?