 Good afternoon, good morning. Good evening. Hello, wherever you are welcome. We are very happy to have you back from a Hopefully very relaxing moral day weekend for you. I am Chris short technical marketing manager at Red Hat on the OpenShift team I am joined today by two fellow Red Hatters, but quick some some some quick housekeeping Keep in mind for our folks joining us on Zoom today and on Twitch that this is a public event And this will live on for a perpetuity even on Twitch. We are going to pull it off and Once it cycles out we will have on the YouTube so it will be on the internet forever. So please Keep in mind that you know we have a you know code of conduct of sorts You know for the the the Twitch stream that we're on they have a community code of conduct So please keep that in mind If you have any questions, feel free to let me know in chat With that we are here for developer experience office hours. I am not the expert on this So we have two of my very favorite fellow Red Hatters Serena Doyle and Jan Kleiner and I will let them introduce themselves Serena take it away. Hi, my name is Serena and I am the product manager of the developer tooling area and I Recently switched. I was the uxd the lead until about two weeks ago. So now switching over to product management But so representing the same product. So welcome. I'll let Jan introduce yourself. I'm Jan Kleiner So I'm here from our OpenShift Developer Advocacy team. I think we may have a few of our other team members in the channel. Yeah I need to mention one more thing. We have several team members in chat actually so Feel free to fire away your questions But also you might notice During the starting soon banner or anything else that we have a follower goal set up We are trying to hit 1,000 followers for the the Twitch channel by the end of June. So please subscribe to Twitch Join us on the Red Hat Twitch or Red Hat OpenShift Twitch and You know subscribe today help us hit that goal of 1,000 followers by the end of June with that Further ado, please take it away. Okay, great So today, you know, we have our office hour I think last last meeting we had in April we talked about starting to do these every two weeks So and on Twitch, so we're excited to be here And as you guys know, we our OpenShift Developer experience office hours kind of like we try to demo what's coming up Open questions for any questions on what's what we're showing today Today, what I'm going to be showing is that I'm going to be demoing what's coming with post 4.4 So I have a cluster that's got like the latest Code on it and I'll be demoing what's coming up soon. So I'm also going to add a Survey into the chat. So as people kind of listen to us and after the office hours complete if you don't mind Just letting us know how we're doing So today if you you can see my screen, I'm showing you the OpenShift console and What you'll see Post 4.4 is that we've made some navigation changes and last meeting. I think what we did was we shared the designs But today I'm more sure I'm sharing the actual implementation So in the navigation area in the developer perspective So I think most of you probably do know this But there's a way to change between the administrator perspective and then switch over to the developer Perspective so as a developer we assume you're going to be in the developer experience most of the time. So In this area, you'll see three kind of main buckets in the navigation The first bucket is kind of task-based navigation. So we've moved some things around but we have the ad page Topology page our monitoring section and search The second section is more object-based. So you have build pipelines helmet project And then the last place is a new area that we've added which we allow users to Add and remove resources to the navigation because this is something that we were asked for in the past so For example, if I wanted to search for pods I can take a look at the pods here and when I do a search you can see over here on the right-hand side I have a link to add that to my navigation So I can click on and and then you'll see it down here So then so now it's really easy for me to be able to go from project to project and be able to see all my Pods if that's the resource that I'm most concerned about You can add as many items as you want To the navigation and then you can also very easily remove them by either using the search again, or you can also hover over this icon Click on the remove icon and then just confirm that so it removes it from the navigation so this is one of the things that we're hoping is going to Enable users to not switch back and forth from developer to admin perspective as frequently as we had heard that people were Frequently switching over just to get access to things like secrets config maps pods and other things as well The next thing that I'm going to just show is that at page So if you have seen this in previous releases, you can see that we've now added more cards here So we've added kind of shortcuts So operator backed is one of our newer cards and this is just going to the developer experience And what it does is it just pre-selects the operator back services. So that's what you can see by default If I go back to add again If I click on home charts, you get the home charts selected by default and We also are enabling You to click on a pipeline Card which should bring us directly into the pipeline builder And as with every demo sometimes things don't work. So it looks like this one might be our time here That's not going to work, but that's what that should be doing And then finally, there's also an event source card and I will wait for a bit because I'm going to show you how that works in a while We've also made some changes to our project page. So we used to see Seeing a lot of problems here, so let me see if I can just Refresh my cluster. There we go So if I select on project, what you'll see now is we have a project page that's got three tabs We have an overview tab, which is kind of like our dashboard We have a details tab, which is the default details page Tab, which is showing just real details from the MMO directly into this page And then we have the project access tab which used to be embedded in like the more section inside the navigation So as we continue to as I continue to demo the stuff if you guys have feedback or questions You know feel free to put things into the chat and Chris will help Moderate any questions One of the things that we're curious on is this project overview. This is kind of a project dashboard, right? and we're curious on What type of information that we're showing here and is this what people are really interested in seeing? So what you can see here is on the top left hand side. We see the details card Which just has a name requester and labels and then we show an inventory card And what this is showing you is the resources and if there's any errors or warnings with these objects You'd also see indication inside that inventory card We then have a status card right now This is just showing that the project is active like so you might if you deleted that you might see that in the terminated state as well And we're thinking in eventually that we're going to add things like application vulnerabilities or other types of items like that up here in the status card We then have utilization card which shows you some of your high-level utilization information and Then if you have any resource quotas that are configured you'd see them at the bottom and on the right hand side You'd see that activity card that allows you to see the most recent activities and events So if anybody has any comments on that again put them in the chat that would be awesome And I'm now then going to talk about health checks. So Feel free to ask your questions. Sorry to interrupt But yeah, if you have questions about anything that's going on right now or you want to slow down and go back to something Please let us know So now what I'm going to do is I'm going to go into the topology Topology view and if I click on a deployment here what you'll see is that we've now added health check support So any deployment or deployment config that does not have health checks Already defined when you click when you select that item on the right hand side of inside of the topology view or in the list view You will end up seeing that This kind of in-line Notifications stating that the health checks are not configured. So this now allows me to you know go back in and say okay I want to add my health checks. I can say I want to add a liveliness probe. So I'll put this here And as I scroll through that I'm just going to take all the defaults and hit check And then I'm going to say add and now you'll see as I still have this item selected my My in-line notification is now gone because the health check has been configured So that's cool. The other thing that we can do and we can also As we are creating objects or deploying images importing from get etc. We have a new Option called health checks. So as you're adding something I could also say, oh, I want to add a readiness probe on this point and Take the defaults and then hit create and Now we can see when I click on this item Also, I don't see the in-line notification. So that means that the health checks have been added. I Also can do an edit health check as well So that's this is the the flow for either adding health checks afterwards editing health checks or Creating them on the fly All right, so we got a lot of questions here in chat Go ahead Serena before before we jump into the questions. I just want to you say how happy I am to see the health checks Come back to the developer console. I think that's so nice not to have to do that with the animal So thanks Yes, yes, yes I am a calendar driven yamal engineer, but I don't want to have to be a yamal engineer if I don't have to So some questions here Jan, do you want to field them or you want me to sure? Yeah, let's see. So the first one is related to projects and Arbac basically so what if the requester of a project left the department or company and we want to associate projects with a Persistent business role. So what would be the best way to do that? um, I Might be more specifics to be able to give the best answer, but Serena I think you know service accounts potentially could be helpful there Do you have any other like as far as under projects? The project access section. Are there any other tips you have around that they'll be helpful No, right now I mean for project access this what we've done here on this in this tab is we've tried to Abstract away the concepts of roles and role linings, right? So that's one of the things that we've really tried to do on in the developer perspective So we don't have any answers for that that here. I don't think at all What we're allowing people to do is just kind of have a few edit or admin role anything like more complex And that we need to go back over to the admin side, right? Yeah, and cluster admin is always going to have access to all the projects and all the resources So if you wanted to set up Different, you know access structures that way you could They'll always have access to everything if you needed to remove access for somebody who'd left the department or something like that Interesting though because it's almost like I think what you might be asking is transferring ownership of a project when somebody leaves, right? I think that's what that means, but it might be something that we can think about a little bit more on our end The next question was around the pipeline builder and the pipeline section in general So the question was basically what sort of pipelines are you building there? Is it tecton? Is it jinkins? What's behind the scenes? So Do you want to take that now go for it? Okay So the pipelines with capital p that we have here is open just pipelines, which is built on top of tecton Um, but as far as you know, what you plug into your pipeline is very very flexible With tecton, but yeah, that's that's what the pipeline builder there is built on top of tecton Let's see. I think there was one more question. I'm trying to follow Through chat here. Oh, which version of open shift is going to have the add to sidebar shortcut feature So four five four six. So we're and when we're talking about I think we're talking about um The navigation Oh the nav shortcuts. Okay. I'm sorry. Yeah, those those are scheduled for four five But not committed to four five yet. Um, but they are currently developed. So The hope is that they'll be in four five Or later Cool See hot up here new question. Is there a view on how large existing jinkins should integrate With the new tecton system We can try and I can try and pull some links into chat. Um, that might be helpful with that I don't have you know broad guidance, but I think we can point you to some References that might help. So serena while you're moving on I'll try to drop something in chat unless my team needs me to it Okay, great sounds good. Um, so let me I'm gonna Go on and just do a couple other small demos So one of the things that people frequently ask us is You know, how am I able to change the logo inside of the some of these items in? In the topology view So for example, example, both of these deployments here I added by doing a deploy image, but they didn't know what the type of workload it was So you are able to add a A label to make this change So if I add a label, that's called And um, let's say that I thought that this was spring boot I can say spring boot Enter hit save and you can see that my logo changes to spring boot Eventually, this is going to be something that we want to Expose and into the UI as well. But right now and you know Um, we do have this capability of allowing you to change that corkis spring boot Red hat. I'll also try another one here, which is red hat spring boot So I'll write that. Um It's a red hat spring boot and that shows me I think it's called a snow drop icon Um, so again, like those two icons support for those two icons is now been added to 4.5. I think corkis corkis is also 4.5 as well So that's a way for you to you know, be able to annotate through labels and be able to actually see a visualization change inside of topology So this is nice for demos or even just so people understand, you know, what the runtime of that image actually is I see a Message that says our custom icons for the pods and services supported right now. No that that is not Supported right now. We don't have it and then in your term on The roadmap either but it's that is an interesting question though. I could yeah back to the UX team because we have regular meetings with them Yeah, yeah, that's definitely I'm sure people would like that Yeah, yeah, that's a good one. We can definitely take a look at that for sure I'm gonna fire that message off right now Okay, awesome all right So Let's see. I am going to switch off now to talk about Helm enhancements And let's see so I'm going to go over to the ad page as I noted before we can click on the home chart card So this page is kind of a discoverability Right allowing people to understand how they can add to their their projects. So if I click on home charts It's been a pre-filter that has developed the panel of the phone charts for me and some of the things that we've added here That will be available post 4.5 is If you look at this info page, you see this whole column on the left This is new right so you can see the chart version app version home page maintainers You can see the email sometimes when it was initially created um We also have more information like the readme file for this chart is here as well um So all of this information right is is provided by whoever's creating those home charts So Some you might see more than others. I'll go to another example here where see this description Here we go. The description is there as well as the readme is there But then I'll go to this one here where you can see there's a lot much let Much more limited data that's shown and again, that's because of whoever has published these home charts For us Serena question about that that came up in the chat. So The question was where are those home charts loaded from and can we add our own? So correct me if i'm wrong, but so in 4.4, which is the release where helm was added in the developer catalog That these are being populated from a very specific Repository of helm charts, but in a future release that setting of where you're pointing to for the helm charts is going to be configurable Is that correct? Yes, right now on the well We have on the roadmap for 4.6 and later. We have ability to have multiple Libraries of helm charts and we also have rugby who is online with us And I don't know if rugby maybe you could give us some more information around What we support today on the 12 5 So right now we support just one red hat supported developer catalog, which is the health catalog that we see and it's a curated list of helm charts that we provide from red hat and I mean, there's a bunch of onboarding criteria where if a helm chart owner wants to contribute to a red hat catalog, they can onboard their chart on top of our catalog and then for 4.6 We have plans to support multiple chart repos Where in the user code go ahead and for example add a plastic report to their catalog and everything will work fine Thanks rugby There's also another question in the chat see The helm charts referencing public images. Can we point them to the local The registry remove any external references we are disconnected install So, I don't know if you have the answer to that No, I don't have an answer to that Probably later versions will have support for disconnected support as well So I have I have thoughts and opinions here. We are working very hard on the disconnected install piece both community and Here at red hat Are both working very hard on getting disconnected installs up To a point where they're easier and it right like almost as easy as the online part. So It's a work in progress. There's a lot to it. Obviously when you have things like olm and registries and the number of things that are needed for just open shift to just run normally, so There's significant effort. There's a work group that has been stood up in the cncf community And we have been working on disconnected installs for a while here at red hat So, yeah, there's lots of work going on there Great Thank you Okay, so what i'm going to do now is i'm going to install one of these helm charts. So in Right now When we're installing helm charts, unfortunately at the beginning we're still using the anal editor That's something that you'll see change we have on the roadmap for four six. I think right now we're targeting being able to change this to Ability to create be a form or anal editor and be able to switch back and forth but for so far right now what i'm going to show is Installing this helm chart be a anal editor And as I install that you can see now we have this helm release created here on the right hand side I'm going to I'll select that and what you can see is I have three tabs here. I have A helm release details I have the resources that created by that helm helm release itself And if they're release notes available with that helm chart, you would also see them here Um, and again that is dependent on whoever's creating that helm chart from the beginning We now have the ability also in um, or we will have the ability post 4.4 Expected in 4.5. We'll have the ability to do an upgrade Upgrades are really interesting because you can upgrade a helm release by either changing the chart version But in this case, I don't have enough of an additional chart version to upgrade to but I could also if I wanted to You know change the ammo and that would be considered as An upgrade. So I'm just going to change something from false to true Get upgrade And then what you'll see here is if I Select this helm release you can see now if I go to helm revision history. You can see that I now have a revision Apologies everyone for the technical errors on my part. We are back at it here and Often rolling again. Take it away serena Okay, great. Sorry about those technical difficulties there. So what we're going to do is go back to um, the helm chart I'm not really quite sure when we were cut off. So I think I I think I was able to talk about everything that's available on the info panel, etc But what I was trying to do was show you guys how you can do an installation of a helm chart and that we also now Support both rollback and uninstall and update. So I've just created install the helm chart. So I have a helm release here and What I'm going to do here is I'm going to do an upgrade and and again forgive me if I'm Repeating myself, but what I was saying is that an upgrade can Be two different things you can either upgrade by changing the version in this case I don't have an additional version Or you can upgrade by editing the yaml directly So I'm just going to change this value enabled value of false to true and what you'll see is when I hit upgrade is um When I go back and look at the helm release itself and Go to the revision history You can see that I now have a second revision that I've done an upgrade What this allows me to do now as well is I can all you know anytime I can do a rollback But what I can do here since I'm sitting on the revision history tab is I see my number one revision And if I had made a mistake I could be like Hey, I want to go back to rollback to my initial revision because I just made a mistake during that upgrade or for some other reason I might want to go back So as I hit rollback It Does the rollback so now you see I have a third revision available And it's now rolled back to that initial state So that's a pretty cool feature that's been added Um And so I just showed you very quickly how we can do an upgrade and a rollback And now we also have the ability to do the uninstall helm release, which is very similar to a delete We're just utilizing the same terminology as we have in in a cli and Because it's a destructive action We ask you to confirm deletion by typing in then the name again and then hit the uninstall and And there it goes. It's gone there So I'm going to open it up for any comments or questions And just checking to make sure that That I'm still alive here. So I think you're very alive Yes, all right Awesome. Um, so if there's nothing else there around helm, I'm going to now Switch over to eventing. So event sources is something else that Uh, we have coming post four four And in order to create an event source, you need to have a A k need of service available. So what I'm going to do first is I'm going to Utilize import from git. Thank you guys lots of you probably have already done something like this where you put your git repo in It automatically detect detects the builder image for you And if you continue to go through all these, you know Defaults are set for you. But if you want to create a k need of service and the resources section, I just click k native service there We do have this ability to Create pipelines on the fly if you want in this case, we don't have a pipeline template available for the python k native service Combination, which is fine. We don't need that. I'm just going to create that k native service If you guys have done this before you probably know that when a k native service is first created It's waiting for that revision to It's waiting for that revision to to come up and the pods to come up before it is displayed inside of the the k native service itself Since we're going to wait for a second or two. What I'm going to do is I'm taking a look over here to the right. Can you specify a post secret in that form? I will show you this Yeah, so inside the import from git you can Um You can hit the advanced git options where you can either reference an existing secret or create a new secret there So I think that would answer that first question um There we go, and now I'm going to just go back to topology. See if this revision is up yet not quite yet So it will Help that in a minute Well, it's going we had another question in chat asking if tecton is replacing s2i s2i is Source to image which is what is being used when you do that git repo Import and it picks a builder image your source code and creates like the application image tecton is not min is a replacement for s2i s2i You can use s2i as a task in a tecton pipeline So they they very much can interact but it's it's not a replacement for s2i Thanks for answering that. Yeah, it's something else that's been changed a little bit is on our k need of service You'll see down here on the bottom left hand side. We do have a logo Well, we call it a decorator that indicates if a build or a pipeline is associated with it in this case It's a build, right? So you can see that our build is just been completed Um, if I wanted to in the right hand side panel you you guys probably might also know this But there is a build section here. And if I ever wanted to kind of view the logs there's a quick one link access for me to be able to To click and view those Build blocks and as it's we see here it's successful. So hopefully when I come back to topology We're still probably gonna have to wait another minute or so, but it's getting there. We do have a revision But the revision does not have A part associated with it yet. Somebody just asked what version of open shift is this? This is a This is we're running the daily build which is um Let's see. I'm gonna ask and maybe Go into I'd like you could show them right now go to Okay, uh I'm trying to think where is it in this for you Actually, just switch over to the administrator view or yeah and about it might show you I I'm not sure what it's gonna say Yeah, so this is a four or five build But as I keep saying Expected in four or five because some of the features that might be here Uh might not necessarily be delivered, but um, this is what we're working on is daily And expected to go in four or five Oh, let's see. Okay. So cool. Finally here we go We've got our revision shown up here. So what this means is I can now add an event source. So let's hope I can Do this properly. So I go to the ad page. There is a card called event source on the bottom This is pretty cool. We now have A number of event sources that we can create through the ui Some of them are form driven and some of them are yaml driven The first four api service so api server source container source Crown job source and ping source are all generated via form in this first version that we're releasing with these And sync binding. Oh, I'm sorry sync binding is as well camel source on the other hand is Yammel driven and in the future and on the roadmap and further You know, hopefully the following release We will have the ability to have form driven and yammel driven event sources and the ability to kind of switch back and forth, but that's That's not yet available So what I'm going to do now is I'm just going to show you an example of creating a ping source Where I'm just going to put in some data I'm going to add a schedule the schedule the schedule is the typical crown job schedule format So I'm just going to put in five asterisks, which means this is going to run every minute The next thing you have to do is provide a k native service or a service to sync to Since there's only a single k native service in this Project it automatically defaults to that so you don't have to worry about that It also defaults to a name based on the type So since this is a pink source the name of this object doesn't be pink source I hit create and what you'll see now is you've got my ping source right here, which is An event source that you just created and it's connected to this revision And this is configured so that in every about minute it will kick off The K native service will be accessed so in about a minute again if we wait long enough what we'll see Is this will go from auto scale to zero to And in scale up to a single pod So again, if there's any commentary that we can have I don't know if anybody wants Jan or or or maybe row heat if you guys have any other discussions around event sources we could Talk about that now although now I see it must have Gotten that information and that k native service is now scaling up If I click on this Again, we can see zero pods right now. It is pending And within another hopeful 30 seconds or so that should scale up and be running There is another question here around are there documents or reading available on how they interacted for four? um Yes, so, you know while you were doing this demo. We were kind of answering a few questions in the chat around tecton and sti and how how you can use them together Okay, we can provide some other other links to those but just to be clear You know tecton can be used with many many other Things aside from sti. You don't have to use sti with with pipelines But if you are using sti and find it confusing and are looking for more information around that We can uh, we can try to drop some stuff in there. Um, if you have any way of clarifying the Specific points of confusion that might help us get you pointed in the right direction Okay, and it looks like there seems to be an issue with this pod coming up Um, I like probably shooting pods. Yeah I'm not sure I do Can you click on events? Yeah, that sure can yeah Oh, it's getting stuff Let's do this thing. It's taking us time. Yeah taking a while. You know, it's off a mortal day weekend. You know Maybe do we want to let this do its thing and then we can move on to whatever was next and come back Sure. Sure. Sure. Sounds great Um, I know that I had tried earlier to click on the pipeline card here I'm gonna do it one more time to see. Yeah, great. I think it's because um There was just a glitch with my system here before so, um, I'm gonna go back again and show so from the ad page We have added a new card even though the pipeline builder was Uh, introduced in 4 4 what we did what we're doing post 4 4 is we're adding that new card here in the ad page to kind of Again, make it a little bit more discoverable Because the other way that you can get to the pipeline builder is if you click on the pipelines Um Navigation item and hit create pipeline, right? So, um, I'm going to just do this quickly Uh, I'll see I don't know how many of you guys have created a pipeline before and um You can create a number of tasks here. I'm just going to pick things by default. You can create either Parallel sequential or not sequential tasks, right? Um, and then as I'm continuing to add these tasks You see that there's a um You see that there's a red exclamation point there. That's because there's missing resources for those So if I clicked on the build a task you could see here on the right hand side that I need To add some import and output resources For that to be filled But there aren't any available because they there aren't any associated with the pipeline itself So I would come down here on the left hand Bottom side of this form and I'd create a new resource of type git So I'm just going to say get resource And I would check the resource type. I'm going to select get type and uh Then I'm going to go back here because there was another one. I think it was image So I can add another resource which is my image resource And select resource type here is image And now if I go back to the build a task you can see Here I can have a drop down that shows me I can select my git resource And I can select my image resource and as I have done that now all my required input is in set And that exclamation point goes away. So I can now do the same thing for git clone, right? So, um I have another actually under parameters I have a url that's Required input. So I need to put a git url to clone. I'm just going to put something in there that's junk For now and That's all I needed to do again. So my mandatory input is is All in and now if I do this third task, you can see that I need to have an image resource selected So select that image resource and Again, now everything is all set. So I can at this point. I can create my pipeline And here you can see the the format of that pipeline is exactly the same so um Some changes that have been also added here are um, we can now see the tasks that are associated with my pipeline That's new in this four five release or coming upcoming post four four And we have the ability to um add triggers. So I'm going to take a look at that modal So this allows me to put in a webhook. So it allows me to kind of um I'm going to ask Andrew. Andrew are you still on the call? Yes, I am Would you mind just talking through the webhook part for me to better describe it to the to the audience? Sure. So the git provider type here would be a selection that parses the incoming data from your webhook So if you go ahead and click on that and Select the first one just for an example here This exposes some variables that you can use that we've Just hit on here on the classical thing These are all the variables that are parsed from the event coming from your your git nico And these can be used in that format there. That's highlighted in that light blue If you go ahead and make use of one of those, uh, those guys inside one of the fields here See what we do revision maybe trying to think what which one would make sense Revision there. So there's a git your there's a repo URL. Let's go ahead and use that one. Okay. Let's do that. Okay I think I can even do uh, maybe not I'm trying to see if I can do copy and paste but maybe not as easy as I thought it might be so let's just do that And then that there would resolve when that event is uh, Is caught on our side here It would resolve into the url that that particular event had which is the repo URL in this case So if I want to now, uh revision I can just add a master And in these cases, there's no git resources and image resources that so it's forcing me to create these right andre Correct if you had some would allow you to pick from those so you can reuse previous created tecton pipeline resources Okay, okay great. And can I just put in some junk value here for now? Just so I can get through the trigger and let's see what that does when I hit add How does that make things change on this page? I see So maybe you can explain this piece as well andre what a trigger template Sure So, uh, there are many resources here for the the tecton triggers in order to make it work here We create a handful of them for you in order to streamline the process so you can get right to using your your webhook This created a trigger template and exposed a url that you take to your Your github page in place in The webhook interface on Your git site to say please invoke a a post request to this url when X happens on my repo a pull request happens a commit happens And then you can trigger this this new pipeline that we're looking at here when that happens awesome All right, so um, so now this has a trigger Associated with it if I wanted to I could also remove the trigger Uh, and I could also start the pipeline myself as well. So, um And again, that is the start pipeline model or form is It's really the same thing as the adding trigger, right andrew the difference is that it just doesn't have the webhook section Correct. So the in order to start this particular pipeline, you have to answer some questions in order for it to fulfill The requirements for it knows what to do Uh during the pipeline. So it's same questions happen on both sides one is just from a trigger and one is made Awesome. Thank you um Are there any other pieces that you think are worth showing here? Maybe, uh Adding the credentials trying to hear maybe we could talk through some of this as well Um, andrew when you do a start pipeline, we do have this new advanced adoption right around credentials Right. So if you're you're trying to access a private, uh repo, uh, you're you're going to want to be able to authenticate it with the pipeline in order for them to have successful access of pulling from your Your private repo So there's different ways to access uh here. So if you select a git server, for instance, if we're talking about our github and then you put in the The base URL that would access that particular site in this case, uh github And then when you pick how you want to authenticate with it, um, you probably basic authentication, for instance And then you just use your username and password or the token that you have and you just use that I'm gonna just type in junk For now, so I don't have it add that there Yeah Under the hood, we associate this to the needed pieces for the pipeline in order to make use of the secret When it's running in order to pull from your private repo Okay, awesome Any questions on that credential section because I think that was another piece that was requested from from some of our users I didn't see a question on that. There was a really good question on is there a simple path to export all of this configuration? So all of this pipeline stuff that you're setting up Um, so that they can turn it into infrastructure talking too fast infrastructure as code, uh using helm 3 for example Do we have I mean whenever you're creating those pipelines, you know, you have all of the pipeline related YAML files, which are modular and reusable, but Is there any other Anything else you're aware of that might help people kind of just like click a button and be able to reuse this So there are some things that we do Provide out of the box here to help out the user. Um, the ad flow if Serena would like to I go into the front and get and we'll just use one of the deployment or deployment configs and make use of that flow there I'm talking about this. I'm assuming. Yes. I am. Yes Yes, so with this Andrea, I'm not sure where this stuff is added or how these things are labeled so that they show up here But they're they're associated with the resource type in conjunction with the run time, right or the builder image right, so A little more detail around that would be there's a There's an open shift namespace project that you can go into and take a look at That The operators created these these pipelines for reuse in order for us to Try to get over there Just open shift. Yeah, it's just open shifts. Okay. There we go. Thank you So these are all the ones that the operator installs on the cluster in order to provide a easy access for the very indifferent resource types and Builder images and that's where that template is coming from. It's one of these Sure, that helps the the question that was asked. Um, but that is People want to create default pipelines for specific resources That is a way to to provide that for your developers so that they don't have to do They don't have to create those pipelines themselves Yeah, I guess that's a little bit different than um Then the question that we had in chat, but um I don't I don't think there's something that's exactly what's being requested From the question in chat where you could quickly and easily export the application specific Configuration or setup to be reused, but that is a really great. Um It's a really valid use case So I think what you can do with the pipelines is whenever you're creating any of these even when it's in the builder what it's doing behind the scenes is there's Basically yaml for each of these for tasks for resources for pipelines pipeline runs all of that. Um That you can reuse. Um, that was one of the nice things about tecton. I guess but um we don't have like a Simple commander, you know, click to export those things at the moment. Um I may follow up with uh Info sec 812 to see if I can get a little more detail from you afterwards. Um, because I'd like to I'd like to talk about it a bit more and we only have five minutes on here Yeah, we could also take a peek into some of the things that are on the backlog. I Can see if there's anything like that that's on the backlog as well Okay Um The I think on the pipeline side, that's pretty much all I wanted to share And unfortunately today, I can't show the command line terminal That's something that hopefully in two weeks we'll be able to to demo Feature right now and my cluster is not working, but it's a pretty exciting Future that is coming up post 4 4 Um And I think for now that's all we have I am going to again request if you know for those of you or are watching live or Um, or watch the recording if you don't mind take the survey. I'll add the link one more time It would be great Let us know how we're doing what we can do to make things better what you want to talk about in the future Always looking for new things Yes Yeah, all right, definitely and in the future I think um, we also might be talking about some of the things that we're looking at for our roadmap for 4 6 and Even like sharing some of the mock-ups that we have for some of those new features So we'd really like to get people's involvement feedback, etc Awesome. Thank you so much for joining us today. Uh, you know just given the Amount of activity we've had today. When is the next time we're doing this? Two weeks from today same slot Two weeks same time same bet channel Yeah, so please join us here in a couple weeks We'll have more fun things for all the developers for open shifts and you know all the other people too, right? Because we're all kind of in this together Uh, thank you jam. Thank you serena again apologies for the Break in the middle We'll make sure that doesn't happen again And I will see you all back here in a few minutes for open shift commas restreaming. Thank you for joining us Thanks everybody. Thanks