 Good morning. Good afternoon. Good evening. And welcome to another special edition of the developer experience office hours. I am joined by the one and only Serena from the future. How are you doing today, Serena? Hey, Chris, I'm doing great. How about yourself? Well, we'll sleep deprived, but you know, that's what coffee's for. Exactly. Looking forward to the three day weekend that Red Hat's given us with the recharge day tomorrow, which is awesome. Yeah. I'll be recharging for sure. Yeah. And hoping we can get through this with some clusters working. We'll see what happens. Oh, yeah. I mean, we have spares, but we never like using spares. Right, right. Exactly. So you want to talk about the new experience in 4.9 coming? Yeah. So pretty funny, right? Because 4.8's just kind of lies. But we've got our developer console team has been working hard this quarter, as usual, and along with a lot of the operator back teams that we're providing interfaces for. And I wanted to kind of walk through some of those features. Some are integrated into the cluster that I have. So we're not at, you know, GA quality yet, right? We're still going through testing, et cetera. And then other things I was just going to show either designs for some of the screenshots that we have on PRs, just to give an idea of what we've got going for people coming into, you know, for the 4.9 release. Which won't be for another quarter or so, but still keep everybody interested in what we're doing. So let's see. I have one cluster which just started kind of misbehaving. So I'm going to try it on this one first. And if we find a failure, I'm going to move to another. So let's, I'm going to talk about a number of different areas. So today, the first piece I was going to talk about are the new serverless features that we're introducing post 4.8. Notice on this cluster, I kind of have a banner. I added a console notification on the top and the bottom that just says, hey, this contains post 4.8 features. Of course on my backup cluster, I don't have that. So we're talking about things from the future on the stream folks. Yes, definitely in the future. So one of the cool features that we've got coming is community camlet support. So if I go into my ad page, you know, there's a I can go into my developer catalog and in that developer catalog, there are event sources. And what you see here is the default for event sources that we provide. If you want. Okay, so I'm going to take a step back. So in order to see this what we have here, we have to have the red hat open shift serverless operator installed, which is already pre installed by me. If you want to in four nine. If you want to be able to utilize the camera community camlets what you also have to do is install the camel K operator. So I've also done that here to operators. Yes, so to operators. If I go into the developer catalog what you're going to what I'm going to be able to see here is this thing called an integration platform. And that's the schema that I'm going to be able that I need to install in order to see the community cameras. And what's going to be really you know what I'm going to cancel out of this one more time because I just want to go back here and show you guys one more time when I go into the event sources right here. It's just showing me for. So now what I'm going to do is I'm going to go back into the catalog. I'm going to install this integration platform in my name space so this can be done per name space. And when I do that, we'll go back. We'll go back into the event source catalog. And now what you'll see is I now not only do I have the four default event sources but I'm also got 50 community cam community camlets which are source camlets. So if I go over into the camlet catalog, which is here, I can see there's a number of source and sinks. But let's just look for the heck of it. I have not tried this because I literally just installed it but I see earthquake source here right so now if I go back to my event source here. I saw Chuck Norr source to but you know. So yeah so you know you can you can kind of create any of these obviously you'd have to have all the requirements ready and stuff in order to utilize them. But what this is really doing is it's enabling our developers who are creating or building applications to be able to have a lot more event sources available to them now with this community camlet integration. So it's pretty cool. As I mentioned us, I said earth so that's why there's only one but yeah so there's 50 of them, you know, just to take a look through and I'm not going to demo installing one. But just to kind of take a quick look there's Bitcoin kind of interesting yeah as you said Chuck Norr's well I'm not sure what that one is. Yeah, periodically get some jokes very nice there you go. I'm really wondering what I can build with that. I know. I know. Yeah. So GitHub source Google mail, you know, I think I think there's slack down here as well. Telegram. Twitter. Wow. Okay. Yeah, so there's all kinds of great things you can do once you pull this in. So, so that's a great new feature I think people are going to be excited about that. Now, the next thing I'm going to do is talk about a little bit of extended or enhanced support that we have for K native services. I'm going to try to create a K native service right now. And if it fails I'm going to have to pop over to the other cluster so let me just say I'm going to deploy an image the hello open shift one. And I'm just going to say, make this a serverless deployment. I'm going to hit create. Oh, it worked. Awesome. Okay. Sorry, because this is, I we just stuff from the future so yeah, the number of machines that so I wasn't sure if it was going to work there. But it looks like it works so thanks to Jeff if he's listening because he just fixed it for me. Okay, so when we install the serverless application, if I select that you can see on the right hand side right underneath the resources tab. We've got pods revisions and routes. So I can access this app by clicking on that route, right. And it's the route that's redefine right so it's that kind of the base default route that we provide. So what we're doing now for serverless applications is enabling or supporting domain, domain mapping. So if I come to my edit my actions menu and say I want to edit hello open shift. What I'll be able to do down here on the bottom and say I see I want to look at those writing options again. It's not a domain mapping here super easy. Yeah, super easily right so if I want it just to be like I could just call it Serena.org or whatever, whatever it happens to be right I could just hit create. There it is. It sets up for me. And now I hit a save. Of course, there's some additional setup you'd need to do in order for that to actually work right yeah. I'm going to click on this object. And now, since I set that domain mapping you'll see that it's also here as well. Right so. So, basically the additional setup would be DNS right just creating a CNAME. Yep. Awesome. That's fantastic. Yeah, so the other cool thing that you can so there's a number of number of different things you can do here. I guess they also have the ability to create a route. It's not exposed publicly so it's called a cluster local URL. So I can also go through that. So I'm going to do another ad container image. I'm going to use a low world. Go I don't know if this one works. I haven't tried this for a while. And instead what I'm going to do this time, instead of creating and going back and editing, I'm just going to uncheck this box. So what that's going to do is it's going to give me a route on my cluster so cluster local as they may say. So when I hit create. This is going to take a minute for this to come up but I should still be able to come here and I can see in that URL that it's set to cluster local. Nice route right so you also then do have the ability to come in here and set a domain mapping from this one as well. So wanted to kind of walk through those two. So I think that, you know, those things. The K native upstream is doing a lot of work in this area and we are, you know, as they're continuing to do that work and we bring that into open shift serverless. We're going to be continuing to increase the amount of features that we provide in through the console. So that stuff is already available if you go in and you're editing amel or whatever but like I mentioned, you know, we're just trying to make sure that we create this, these easier experiences through the console today. So that was a that's kind of a nice one that's going to be in four nine question and chat here. Okay. What is under the hood of the domain mapping. I'm assuming the load. The ingress is part of that but the route itself is set up by the load balancer if I remember correctly. I think I have I brought the link with me just in case some questions were asked that I did not know and I'm wondering if we'd be able to take a look at that this year. And we can maybe even stick that in the chats. Sure. This is, let me find this. Let me get the link and I'll stick it in the chat as well Chris. Maybe you can take a peruse through and see if that might will do. Yeah, I don't want to give you any information. Because I'm not I would have to read to find out that detail and I'm not sure how quickly we can find that. So if you're using Istio creates Istio gateway but that's yeah ingress router. Okay. And actually it's ending up that hello world example in the docs here so or hello. I should say yeah. Okay. So yeah good to know. Great question. Thank you for it. All right. So the next piece around serverless. There's a couple other small things that are going to be done here so in. I think it might have been in force seven what we did was we have even been for six that we enabled visualizing channels and brokers in the UI. We had even had a form based channel creation, but we did not for broker so the so if you go to the ad page in four nine what you'll see as a broker item that will be available that you're just going to be able to create a broker through the you know through a form rather than having to do it through YAML. This is currently just supporting kind broker so it's only one type of broker that we're supporting through the creation format. And when you create that there's a you know a unique visualization here. And then you can create your your add your triggers and connect those to your key native service and add filters and values as needed. But that feature has always kind of been here in the well nice and sales last couple of releases it's been in the console we're just exposing a form driven experience for that creation of the broker which is nice. The other thing that's going to be changed on the ad page for serverless stuff is today in four eight, we have a serverless card. And we also have event sources that are under the developer catalog in four nine what we're going to do is actually rename serverless to eventing. And we'll have event source channel and broker all under that so as the operator is installed you get a single card that shows all the stuff that's eventing related in there, which makes a lot of a lot of sense. That's just kind of a little bit of a usability enhancement there. So, moving on to another area that we're making changes is in is monitoring. So if you guys notice in our navigation underneath apology, instead of monitoring we have renamed it to be called observe. Nice. I like this. So, yeah, so we're trying to you know because as we're moving to a we have plans for continuing to enhance our observability story. So, over the next, you know, number of releases I'm sure you'll see additional things or features enabled here that will help with that story. But the first one is making that called observe into apology when you select up an item. Actually, we don't have it. Let me just put a regular deployment config. Right now we don't support that feature for serverless applications. So if I select just a regular deployment. You'll see that this tab here is called observe it used to be called monitoring. And there is a link that says view monitoring dashboard that's also going to be changed to be observed dashboard. That's really not that exciting. It's literally just the, it's just the name, but the other thing I do want to show you is the PR. So hold on for one second, I am going to pull up that PR for you guys because the PR is not merged yet I was kind of hoping that that was going to happen before our demo occurred today, but it did not. So one of the exciting things is, and this is a screenshot from the PR is, let me go back to what we have today again I'm sorry. If I go to observe. We only have a single dashboard today. What we're doing in 49 is we're going to have for dashboards. So there will be a dashboard selector. So this is one of the screenshots. I'm just going to go back and pull over the other screenshot. I'm just going to go back and pull up gif. Whoops, maybe not as big as I might want it to be. And I increased that. Let's see. Yeah, we go. So yeah, there's a, there's a workload dashboard. There's a pod dashboard where you can do it in context and this is a little blurry because I had to increase that so sorry about that. So if somebody went into the CMI logged in as admin here I might be. So you know in the administrator dashboard. It might take me a few minutes to figure out where that is over here. Or maybe I'm not. Oh, you know what, I am not admin. I'm not admin there. I'm not seeing the tabs I would normally expect. Here we go. Here we go dashboards. So you know on the administrator side for administrators we have all kinds of dashboards much more. What we're doing in 49 is we're just exposing four of those on the dev side. We're also talking about having thinking about a mechanism where as people add dashboards here they might be able to tag them to show up for developers. That would be post for nine, but that's something for, for example, the Canadian team has been talking about this that they want to really be able to enable their serverless applications to have additional dashboard, you know, monitoring and observability use cases fulfilled so that's something that we're looking further down the road after for nine. But this is we're hoping that this kind of sets the stage for that, which will be nice. Yeah, I'll say. Yeah. Okay, so I'm going to go back to my test cluster. Alright, so the next piece that I have is around pipelines. Now, again, for pipelines, most people do know this but you need to have the open shift pipelines operator installed in order to have the pipelines items show up in the and the navigation on either developer or admin side. But what we've done is made some major improvements inside the pipeline builder for people. I don't know if people had done this previously when we did add tasks what we did was just show to drop down of the available tasks just with the name so if you didn't know what that task name did, you were in the dark. So the first thing that we've kind of done is add the search capability so I can just type in let's just say maybe. Okay, let's yeah, so I'll type in get so now this shows me all of the available tasks to me, not only so it shows me some tags and some labels here so I can see this is a red hat community one this is actually from red hat. But it also shows me that little description on the right hand side right which so enables you to really be able to know what you're doing without having to get out of the workflow to be able to know what time task you're adding. So that's one really nice piece the second piece which hasn't been merged yet is so what I'm showing you right now is it's just showing you the tasks that are in the current namespace as well as the cluster tasks. But what we're also going to be doing in 49 is we're going to be integrating tech town hub. So all of these tasks that you see here in tech town hub when I say kinds tasks, all of these will be available to you when you're creating pipelines from our pipeline builder in 49. So we'll see those all in this, the same search, search dialogue. So, pretty cool because I don't know the number of these because it's not showing me the number but it is going to expand the capability right off the bat for you if you want to use something from the community. Immediately, right. Pretty cool. And then. So again, so this is again talking for the future that will be in 49 this is something that we have kind of like I mentioned, there's PR is up for these posts for nine or talking about doing is the pipelines team has already started talking about having the capability of having your own local tech town hub. So, I have my own curated set of tasks on my own cluster right. And so, post for nine, we would also integrate integrate that capability once we have that API we would be able to hook that into this workflow as well. I know there's a number of customers who are have been asking about that so just kind of mentioning that as that's something that we will be looking at post for nine as well. So yeah, so that's pretty cool. Let's see what else have we done for pipelines. The other thing I guess what we are doing is we're going to be supporting pipelines as code. This is another one that I'm going to have to show you the PR so give me one second here. I'm going to copy the link and pull us over here. And so today. So this again this is a screenshot of a PR that's up for review. And for eight what we do is we only show pipelines in the UI, if they have a pipelines resource associated with them. What pipelines as code is doing is enabling us to look at a get repo and find pipeline definitions in that get repo which are considered pipeline is code. So this is like source of truth right that pipeline is code is now in get. We are able to run those pipelines and then I'm going to show you another. So as that pipeline is run, you would still be able to see you would still be able to see the pipeline runs associated with it like you do today. It's just that rather than creating pipelines through a Kubernetes resource, you're actually having it look at your get repo and your pipeline definitions right from your get repo. Which again is another thing that's been asked by quite a number of customers so this is something this is a dev preview feature for console that would be released in 49. So I think this will also make people excited, you know, whether your tech time pipelines user how getting more closer towards get ops, etc. Right. So those are the two main areas in pipelines that we are are working on. Speaking of get ops at three o'clock get ops guide to the galaxy will be on the channel so please feel free to tune in for that. Who hosts that with you. Is that Christian Christian. Yeah. All right. Mr. Get up some self. Yeah. There you go. Awesome. Another thing that we're working on is user settings which is kind of interesting. So today, you know we have the avail ability to kind of remember settings right so let's see if I leave. Let's see if I get out of I'm going to just throw an example if I get out of open shift when I'm in the administrator perspective, hypothetically, it's going to remember that. And if I come back in here and come in. So yeah, still in administrative perspective. So now what we're doing is we're just starting to expose some of the user settings in a in a form form based flow and give me one second because this is again something I'm going to have to look at in the PR. What we're going to be doing is just some small things initially. See you. We're going to be exposing just a couple of the items that I'll show you here and again this is just a screenshot from the PR. So if you get it from the user menu, there will be a settings item, and then that was not the right one. Hold on. Which PR. Either either the PR I went to the wrong one or the copy and pasted now one of the two. Let's say nothing can ever be easier. Let's say go here again. Copy and paste. There we go. So, here we go. So for now what we're going to be doing is having general settings the first PR is just as general settings so what's my perspective it can either be set to what up last feud which is what it is today right whatever you leave as it returns to when you come back in, or you can always come in as admin or always come in as dev. Also, setting a default project we'll be able to do that through here as well as topology so I think people know for the most part in our topology view today. We kind of have two different versions of it. Interesting here what happened to my. We've got kind of like this graphical view, and then we also have this list view. So that's that other setting is allowing you to, again, you can say last feud or you can say graph or list. So again, these are some, you know, small user experience or usability issues are enhancements that we're trying to pull in to get people a little excited about kind of the usability story. There's one that we have in the backlog, which I know we've talked about here before, and I'd still, I would love to hear from users tweet tweet at me at Serena Marie 125. If it's a if it's something that you guys are interested in is the dark mode, right. We've been talking about this one for quite a long time, and how important or not important it is to developers or users using a console. You know that's a question, and I'll drop your Twitter and chat. That would be great. Serena Marie 125. Yes, exactly. I know it's not something that makes you want to purchase or not purchase something but sometimes it just makes the, you know, your experience that much better or not depends on the people, but I'd love to get some feedback if people are passionate about it one way or the other. So Serena is out there on the interwebs. Yeah, awesome. Thank you. So something that we had done in four dot eight was we enabled, you know, the, the form based edits for deployment configs and deployments. This is something we are also going to be doing for our build configs that's not available in a period so I can't show you that but that's another thing that we've kind of got coming up. And another big feature that we've got in the works but don't have anything to show at the moment is being able to export your application so what we're going to have is a new button here that just says export out. And what it's going to do is give you a tar file with the animals of everything that you have in your current in your current namespace and what that will allow you to do is share it with others or, or the other thing you could do right is change your namespace come here into my import import YAML you can drag in multiple YAML files at a time one spot right recreate. But what this is really doing is setting us up for that capability of when you're integrated with get ops being able to export and put up a PR or shut my sync off for a second I'm going to do some changes in the console and then I want to automatically resync. But those are things that we've kind of gotten that outer loop backlog of where we want to go. And in our working on some of those supporting features to go forward. That's awesome. Yeah, I mean like, you know, just from a get us perspective. So I would want to check things in as opposed to going through each object and getting the YAML and saving it as a special name and everything like just give me that. Let me check that you know, and as you know I see fit, you know review it, you know, modified if need be check it in that's going to be an awesome feature I can't wait for that. Yeah, yeah, it's really cool. And it's been. Well, once we have that ready, I think we'll come on and we'll demo that what that looks like today and also give credit to the teams that have been working on it because we've got some some some people on the CTO office we've got some people in the migration toolkit office who are doing kind of that back end workforce as well and it's been a really nice collaborative project that we're working on and like I said dev preview initially. But then we continue to see that kind of like really working and providing some great capabilities for like for the get an option mentality going forward. Yeah. No longer be thrown over the wall or it works on my machine like it works on our cluster. Right. Right. Can't get much better proof from that. Yeah. Yeah, exactly. So, I know it's only 30 minutes in but that's kind of what we have today that I can even give you the demos of and talk through. But I'd love to have like I mentioned I'm glad you gave put my handle Twitter handle out there anybody interested in learning more about any of these features or feedback. Yeah. Yeah. We're always looking to get feedback also of anything that you might have in your mind that you don't currently do and want to give me some feedback bad good in different doesn't matter right. So you brought up dark mode and it's almost like well everyone else has done it. We should probably add it at this point you know it's like one of those things where it's like, never saw that becoming a thing but okay. Right. Yeah. It's in my OS now so yeah. I know the thing that was funny to me was that one slot got it. I heard everybody slot you know in the slot channel like oh did you see the dark mode right so like people are certain people are really excited about that I guess you know it's easier on the eyes for some. Yeah. Sometimes people like to change the mode to based on if it's lighter Darko. Yeah. Yeah I do wish it was more granular and could like follow the sun better right like I know there's the you know whole thing for like after dark like I want it to happen all day long. Yeah. Yeah. Like light mode in the morning to wake me up and then by about four o'clock switch me back to dark kind of deal and I'm sure I could trigger that somehow but I want it to happen universally. Right. Right. Yeah, that would be that would be a fancy feature. Yeah. But we just need to start with it. Right. Right. So I know our pattern fly team has been working on on a POC on how that would look from a pattern flyer design system perspective and we even started like an initial POC for open shift around it but haven't discerned if if or slash when that will make our roadmap. So, so yeah the more people we hear about it, the better off it will be. So definitely let us know. I think the other thing we kind of touched upon a little bit earlier was around that observability story so you know like another thing. The observability is just a hot thing right now. Yes, one of the many things right now right like getting better telemetry out of your apps so you can make better decisions with your infrastructure. Right. So the goal, a cost savings experience that you can get from it and then be performance knowledge right like you know your app is going to perform the more you can plug into it. Right. And that's kind of key. Yeah, the key part of the ability is tracing and monitoring and you know logs and everything else. Exactly. Yeah. And you know our topology of you today we're not showing like some of that. Log being able to show some of them the traffic information but we're not doing that today. We have we are talking with a PM that's associated with tracing on how do we pull that in for an integrated observability story. We're also talking to the team that used to what it used to be Java mission control I think it was called before where they create recordings now they are creating a an operator. That's called cryostat where it allows you to create some recordings so you can see some some data around your Java applications. That's something that we're hoping to provide an operator for that would extend the UI from a monitoring perspective or observability perspective. Post four nine. So we're working with them as well. But we also have a number of we're starting to try to get a number of workshops of customer empathy workshops around monitoring and observability, we're trying to do them for both the admin space as well as for the developer persona. So again if that's something that you're interested in please let me know I'll probably even tweet about that so I know our UX team is I think they said that in September time frame we're thinking of starting some of those up. So it would be great because what we're looking for is customers from different companies you know obviously it'd be a four or five in the same company that's great as well. I'd love to hear the voice from many different developers from different companies from companies exactly. Exactly. Yeah, yeah, the more info the better off we are the better solution we can build for sure. So, lots of opportunities to kind of influence the roadmap I'd say, yeah, and give and give your perspectives. So, wonderful. Well thank you for coming on Serena. Yeah, all of this. It's always so cool to see what you all are up to in the future there. Yeah. So thank you again tuning in and thank you for coming on Serena and we'll catch up next time. Definitely kudos to the dev console team and everybody who's worked hard on all this and thanks all for joining or watching later on. Yeah, thank you so much. You guys soon. Stay safe out there.