 Hi everybody. Today, welcome to the What's New in OpenShift 4.10, the developer edition. I'm Serena Kekli-Nichols, and I'm Product Manager for Audio and OpenShift Dev Console, and I'm here with a bunch of my Product Manager friends. I'll hand off to Parag to introduce himself. Hi, I'm Parag Dev. I'm the Product Manager for Developer Sandbox, the upcoming App Studio offering and the dependency interface. I'll hand it off to Steven. To Rob, I think first. Oh, sorry Rob. I can't see. No problem. I'm Rob Gormley. I'm the Product Manager for OpenShift Builds. Hi, I'm Steven Le Meur. I'm Product Manager for DevFile, SBU, Helm, and GQ. Yes, Tori? Hi everyone. I'm the Product Manager for Code-Ready Workspaces, rest in India, Bangalore. Mohit? Hi everyone. Good morning. I'm Mohit. I'm the Baser of India and I'm Product Manager for ID Tooling, and I'll pass over to Shyamukh. See, I'm here for our OpenShift Product Management Team, looking after some of our new products. Awesome. Thanks, everybody. So this presentation is in addition to the presentation, which the broader OpenShift Product Management Team recently presented. But today we're going to be focusing on the developer and DevOps personas. So just a reminder, back in February, you did see our what's new Dev Edition presentation, which focused on a look ahead in the next six to 12 months. But today's session is focused on what's being delivered in 410, as well as alongside 410, right? So feel free to use the relevant slides in this deck or customize and make them your own going forward. We'll start with a quick look back at our priorities for 2022, aligning both with Red Hat and our Product Port Fully Ovision and Strategy. Our major priorities were around managed services, onboarding and platform adoption. Today you'll see some of the progress that we've made on these priorities with the release of OpenShift 410 and more. So let's get to it. We're going to start by deep diving into the pieces of OpenShift itself, operators which unlock additional features, as well as tools that ship next to OpenShift, all of which enhance the experience and productivity of a developer or DevOps persona. And I will first hand off to Kastori. Hi, everyone. Good morning. Thank you. And let's talk through what's new in 410 Workspaces this quarter. This year we're focusing on our architectural switch to their workspace. And as you see in the slide, we're also going to go with a new name. So this is more to align with the overall portfolio branding. And our new name would be Red Hat OpenShift Dev Spaces. Next slide for me, please. Thank you. So this year we had two releases so far. Kodori Workspaces version 2.1.0 and 2.15. The enhancements and changes are aimed to making the product very much simpler, familiar, faster and clownative. As you all know, our key personas are administrators and developers. And this quarter we have a bunch of enhancement that would enhance their experience with their product. The big news is Kodori Workspaces now support IBM Z and the next one. It was a tech preview last quarter. Enhancement to the administrators include improved memory consumption, setting parameters like CPU quota. All this is to ensure that there will be no container initialization failures and it's a success and it's a breeze for the administrators. Administrators can also now set storage size to align with the storage size supported by the private cloud provider. So this was one of, these are a couple of big asks that the administrators wanted. So their lives become much easier than what it is today. From a developer's perspective, the aim is to make the product more familiar with the tools and align with what OpenShift Console provides. Support for DevFile v2, providing new navigation link, allow developers to open OpenShift container platform web console from the dashboard through this link. And like I said, we are going through the switch to DevWorkspace. So we also have in 2.15 a tech preview on how DevWorkspaces look. The reason why we are moving to a DevWorkspace engine is life becomes much simpler and easier for both admins and the developers. For admin, it would mean the authentication and managing the workspaces is much simpler and easier and flexible. For developers, we are bringing in plethora of familiar tools and also support for VS code, IDE, BEYOND here and JetBrains, which is the top ask from the product. So that's what was done in this quarter and much more coming up with both rename and switch to DevWorkspace. That's pretty much from my side. Thank you, Anu. Thank you, Kasturi. On DevFiles, DevFiles are the way we are defining portable developer environments, which include all the tools that are needed for the development of an application, either from inner loop and also from the outer loop point of view. Next slide, please. And the outer loop is actually something that is new and that we had into the version 2.2 of the specification. So we had the support for Dockerfile build and deploy into the definition of a developer environment defined with a DevFile. The DevFile public registry is now entirely available from audio and from the developer catalog in the OpenShift Developer Console as well. And we have been setting up a DevFile registry for the Red Hat products as well. A lot of efforts have been done on revamping the documentation and helping the community and also our customers to build their own DevFiles as well. And last but not least, on DevFile, we have been accepted as a CNTF sandbox project and we are also getting external contributions from AWS and JetBrains. So there will be more things coming on this front as well. On the Maven and Gradle Java tooling, so this is mostly about G-Cube which enables the Java developers to build OpenShift Kubernetes artifacts with ease. It allows to either generate the containers using S2I, Docker or BIB or generate the manifests that are needed for Kubernetes, could be for Kubernetes, Vanilla Kubernetes, OpenShift, but also generates end charts. It comes as a Maven plugin and the Gradle plugin is also something that is new and that we had recently and which is getting a lot of improvements at the moment. On the next slide, please, we have just released a version 1.7.0 which is now available in this latest version. All the images that are getting generated are now using Java 17. As I mentioned earlier, we have been doing a lot of improvements related to the Gradle support, especially on Kubernetes and OpenShift side where we had the support for Vertex, Micronaut and Open Liberty generators as well as a number of hardening tasks and bug fixes. On the generation of Helm charts directly from G-Cube, we had the ability to use YAML source files and also we had a way to configure parameters, variables and the values that YAML from a Helm chart through XML or DSL and using the dot notation as well. And as a good news on the project, we just reached the hundred of contributors on the project. So that's good and that's showing a good health of the project as well. Ending over to Moit. Thanks, Steven. Hello, everyone. So I will be basically discussing what improvements we have done with respect to IDE toolings. This quarter has been really great for aligning our portfolio with respect to all the ideas we support including Visual Studio Code, IntelliJ and Eclipse. And these are some of the products which we currently have and the enhancements through what we have done. I'll start with OpenShift. One of the major improvements with OpenShift extension on Visual Studio Code and IntelliJ is that we currently allow users to connect and provision their developer sandbox. Previously, user could have started their local OpenShift cluster using code containers directly from the extension. And now we have also enabled them to provide one more way to run OpenShift and that's for developer sandbox. So anyone who's working on with their OpenShift cluster, they can just provision the sandbox instance from the IDE and start working on it. This will be a continuous work and will continue in the next quarter too. One of the major improvements what we have around serverless functions and Knative is that there is a new workflow which we have enabled for developers both in Visual Studio Code and IntelliJ with respect to serverless functions and the extension is released on the marketplace for both Visual Studio Code and IntelliJ and we will be getting more collaboration around different upstream community including VMware and other folks. The other major contribution around IntelliJ is that we right now have a support for Kubernetes extension. We allow people to work with the Kubernetes clusters and see all the cluster management, the logs, and allowing them to work with the cluster with push of the workspace projects. So that's active development which is happening with respect to Kubernetes on the IntelliJ environment. The other scenario around Tecton is that we allow people if they want to continue working on their Tecton hub or Tecton custom task catalogs, they can directly work with their clusters and the support is also available both for Visual Studio Code and IntelliJ. One of the major improvements what we have around Core AD Workspaces was that in the previous release of Core AD Workspaces where the OpenShift extension was added in the J Registry. I used to support an older version of DevFile but now it supports the latest version of DevFile as Stephen mentioned it slides me. We are trying to make sure that we have the support of DevFile across our portfolio and this is one of the major additions what we want to have with respect to the customers using Core AD Workspaces. They'll have the support of DevFile we do in that and they can start using the OpenShift extension on top of it. One of them announcement around Red Hat Core AD Studio there's going to be a sunset of Core AD Studio which is going to happen next month around April 14th which means that there won't be any further release of Core AD Studio but the work which is happening around Core AD Studio will continue to be actively worked and developed on Jbox tools so that's an upstream project supported by Red Hat and the collaboration which was happening on Core AD Workspaces will still continue to be on Jbox tools side. So that's a brief update what we have around the ID tooling for products and now I'll be moving what we support around the languages. So Red Hat has multiple set of extensions in the VS Core marketplace which supports languages such as Java, Quarkus, YAML and these extensions are one of the top most used extensions by the developer community. Java has approximately around 15 million installs and we did a new release this month itself, 1.4.0 and the next release is coming out in the next month itself. One of the important features around the Java release was that now users can also run the pre-release versions of the extension. This works on the same lines of how we used to run the nightly base. So now from the VS Core ID itself they would be able to select any pre-release and start working on it and providing feedback or see how the features will be rolled out in the major release. Another important workflow around Java extension is now it has been released based on platform specific and now based on a different platform the extensions have released and we now support macOS M1 with respect to macOS inter what we have previously. So that's one of the improvements around VS Core Java. With respect to VS Core Quarkus we did a release after a very long time but this release is pretty much very significant because it allows us to have a language support for cube templates. This was a very important milestone for the VS Core Quarkus and there are multiple blocks which are out and there will be one more release which will happening soon around the support around the templates and the cubes language server. Another important factor was there has to be a collaboration between multiple ID extensions what we support for our portfolio and the VS Core Quarkus and OpenShift extension is one of that integration so now you can directly deploy your Quarkus application on top of an OpenShift cluster using a very discoverable deploy to OpenShift command so that's one of the major enhancements what we have done. Moving on to VS Code YAML this is also one of the heavily used ID extensions for developers it allows approximately as mentioned 8 million installs and we continue working on the built-in cumulative support what we have we have also made change into the YAML parser which basically works that specific to your YAML version you can work on your YAML files and that will basically is going to enhance your developer scenarios so this is what we have briefly from our portfolio for both ID tooling on the language side and that's what I had so thank you moving on to the next one Serena Thanks Gohan So I'm going to talk about ODO a little bit now so as we mentioned in our what's what's next presentation last time we talked about ODO v3 coming out and focusing on three major goals onboarding with guided experiences providing inner and outer support as well as consistency between our entire portfolio so what you'll see coming out in the next month or so is an announcement for our initial dev preview of ODO v3 you can see an example here of what ODO and it kind of looks like with the guided experience and then on the next slide here what you'll see is an example of what ODO deploy looks like with the guided experience so as I mentioned dev preview will be in April and the following commands will be available in dev preview log in and log out ODO in it dev deploy preference build list delete version and noodles and tech preview is planned for summer of 2022 including the remainder of our plans commands for ODO v3 so be on the lookout for that announcement and a blog as well showing exactly what will be available now I think I'm going to pass back over to Sivan speaking covering Codradi containers today because Steve is on PTO so Codradi containers is going to be renamed OpenShiftLocal by May so that is a major shift similarly to the change in the name of Codradi Workspaces we want a better alignment with the brand and with the different things that Codradi containers was allowing to do and it's really about running OpenShift on your desktop so it will be renamed OpenShiftLocal by May so what's new on Codradi containers sorry we have work on getting a smaller footprint during the download so the bundle which is getting downloaded initially is smaller and then during the installation phase of of Codradi containers it will download the different things that are needed for Codradi containers there are two different presets that are now provided so the default one is OpenShift but you can also use Codradi containers to install Podman which is much lighter to run the containers or a local environment along with this there is also a new electron based tray application which allows the developers to directly interact with Codradi containers or Podman it also provides a guided workflow to the user after the installation of Codradi containers so that everything is getting set up properly and that's it for Codradi containers moving to developer services and starting with Helm so as you know Helm is one of the most popular packaging mechanism and we are continuing to integrate its capabilities onto OpenShift so in the latest version of OpenShift we are supporting Helm version 3.7.1 and we continue to provide an integrated experience within the developer console so that the developers can do self-service consumption of the M-charts directly from the developer catalog. The developer catalog can be extended so a customer might add their own custom M-chart repository either at a cluster level which was already available and now with this new version of OpenShift we had the ability to configure a custom M-chart repository at a namespace level which will require less permission as well so that enables the developers to configure the M-chart repository for their own needs in a more constrained scope in fact. We also are providing a certification process for our partners who want to distribute their products using M-charts so we have new charts that are now available including Firewire Orion, Node-RED for IBM Edge Lacework Adjunct or Solace Pupset Plus as well and some others as well. So that's for Helm on service binding is really a way to enable the developers to easily connect their application to backing services. It manages the data plane for the application and the backing services by injecting all the binding information directly in the application workloads so that the application can leverage the connectivity information more easily. So we are providing a built-in set of bindable services which are enabling the Red Hat portfolio our managed services and some other popular services so we have extended that as well. On the next slide please on the managed services we have managed Kafka, Roda and there's few demos that are available and we are also providing support for some popular operators that are existing elsewhere. In this new version of OpenShift there have been addition into the developer console to make it easier for a developer to connect an application to a backing service and Serena will cover that in the developer console section. Thank you. And now ending over to Tiamac. Sorry. So on the previous slide you would see OpenShift builds is following a pattern earlier today and we are not doing it yet but it is working its way through the process. Some updates here. We continue to release more functionality and features into CSI drivers including the ability to handle projected resources Red Hat entitlements simple content access certificates and so forth and allowing those to be shared in a manner that supports namespaces and other kind of access control that it's there to. Similarly we also are allowing CSI volumes to be mounted into a build. This will help support those secret stores, projected resources and so forth and allowing them not to allow secure credentials to be required to be stored in container images there. We're also looking at the ability to build images using the source or binary of your local application and your workstation and we shut up into your OpenShift instance there to. Superite builds also supports custom annotations and volume support there too. Next slide. So as mentioned one of the things that's important to note is that V1 builds which we'll probably start referring to as V1 builds or classic builds is not going away and in fact you can continue to deploy V1 builds and maintain them as well as the V2 builds which are based off of the Shipwright upstream and those can coexist quite contently in parallel. Jenkins operator has been deprecated as a level as of 4.10 and will be not receiving any further updates and we're moving more towards the pipeline as a service methodology there and with that in mind we're going to be continuing to work on improving the builds operator get it updated and into the operator hub there to provide that functionality in that more native fashion there. That is all from OpenShift builds. Alright, OpenShift pipeline so alongside of the Shipwright 4.10 pipeline is V1.7 will be released. The highlights of this release are pipeline as code that reaches take preview that enables GitOps workflows for the CIs. Pipeline will live in the Git repo and the executions will be on the cluster. Kickdown chains is an autopilot of this release that is reaching take preview and introducing into the product that enables once configured customers can automatically sign any images that are built within the pipeline using a variety of cryptographic schemes like Cosign from 6-store X599 or QLAS and other mechanism that are experimental at the moment. Kickdown Hub is introduced as well in this release as a take preview feature so customers can enable Kickdown Hub on the cluster to give them their own version of Kickdown Hub to be able to create a list of tasks that they want to expose within their organizations to be used by their dev teams and SRE DevOps engineers to build pipelines and another area that is highlighted in this release is taking advantage of user namespaces in OCP 4.10 to be able to run tasks in that namespace which allows the it opens the door for type of tooling that required to run privilege and open shift like Builda to run as a root within the container but since it's running the pod is running user namespaces it's mapped to a non-root user on host that would essentially remove the need for those tasks to run as privilege pods on top of the platform and also any other tooling that customers might have that has this requirements and there are a variety of improvements within the pipeline UI and dev console as well and I think it will go in more detail through as well next slide please GitOps 1.5 also will be available on OCP 4.10 that brings along our OCP 2.3 the highlights of this release are additional new generators and application sets is a hugely demanded capability in Argo CD that allows customers to generate applications based on the Git repo or the list of clusters in ACM or some of the other aspects and two generators are added in this release that allows us to allow customer to configure or seek Argo CD to create an application for every pull request so that it can create an application sync the content of the pull request to a namespace perhaps in order to deploy the content of it and run tests against it before accepting the pull request and merge generator is also added that allows merging the result of two different generators for application sets. The other improvements are more enhancements around control over how certain fields need to get ignored when Argo CD syncs manifest to the cluster this is important when there are objects on the cluster that have multiple owners there might be an operator on the cluster that owns part of an object a custom resource on the platform and you want to have a different part of it in the Git repo and you want to instruct Argo CD to ignore any of the differences on attributes that are that Argo CD is not in the owner or someone else is making changes to it. Next slide please. Yeah. Okay. So now I'm going to do a deep dive into the developer experience inside of Openshift console itself. So in 4.10 we focused on improvements to building your application, modernizing your application and portfolio enablement specifically around serverless and pipelines. So the first page the first slide here I'm talking about we now have this capability of doing a quick search catalogs from the app page so we introduced this icon that looks like a book or catalog in a topology view a couple of releases ago we're now also including that into the ad page which just allows users to quickly search for an item available in the catalog rather than having to browse so it's a nice efficiency type of improvement in addition and if you go to the topology view inside of the dev console which is also an admin side we now have the capability of doing filter by label so it used to only be filtered by name. We've now introduced the ability to filter by label as well. This side panel when you select an element inside the console we have that side panel top open and that is now resizable and not only is it resizable from the width perspective but that width is remembered per user so the last selected item is also remembered per user per project per session so if I'm in this project and have my quirkus quick starts deployment selected and I move over to the observe tab and then come back to topology that selection will be remembered so again just some user usability enhancements here inside of topology another thing that we've done around routes inside of the developer perspective is when we're doing import from git in deploy image we're now defaulting to secure routes in doing that what we also did was we are now exposing these defaults for our forms inside of user preferences so inside of in a top banner in the user menu there's a user preference section now that we released last I think in 4.9 and we've now added an applications tab which allows you to set your routing options that are used as defaults for those those two forms in import from git and deploy image we've also made some minor improvements around just the general developer experience for front-end devs so we got some feedback saying that people wanted to be able to quickly and easily kind of copy the route rather than just navigating it through the route decorator so what we do now is as you go through your import from git flow we are producing a toast notification which has the ability to either drop right out into that new route or copy and paste it and then we also have that copy capability inside the resources tab of the side panel for that route as well another thing that we've done is in the import from git flow if you are importing a node app and using the builder image piece rather than dev files we do provide or expose the capability of providing optional parameters for npm run and again so that kind of helps some of those edge use cases which build weren't able to successfully build by default so you do have the ability to do this now with node applications working off is something that Stevan had mentioned earlier the create service binding action now does let you create service bindings in addition to dragging them so before it was just a drag in the drop of an arrow we now have a create service binding action that's available on deployments with that action all you have to do is you get a modal all you have to do is open up is enter the name and select the bindable object that you want to bind to so when you drag that connector handle from a deployment workload and drop it onto a bindable service we also have a different flow where I mean it's the same flow but we're providing that default that bindable service is already defaulted for you and you just enter the name and you're all set and ready to go so again making this command much more discoverable as well as easy to use another thing that Stevan did mention was extending the developer catalog with additional helm charts right so the CR name is called project helm chart repository what we've done in 4.10 is we do have a quick start available so if you look at the helm chart catalog we do have some text in that description that allows you to enable a quick start right now we are only able to do this through Yemo but this quick start steps you through that process of being able to create that project helm chart repository and expose additional helm charts inside the namespace that you're working in moving over to the serverless area we have a number of improvements there as well we're now utilizing event syncs and topology currently the users or developers are not able to create these through the UI but post 4.10 we will be enabling that through the catalog right now what you do see here the red arrow is pointing to what the event sync looks like it's the same symbol the diamond shaped symbol as an event source the difference is that it does have a pod inside and additionally if you see where the label is there's different icons depicting an event source versus an event sync when you select that event sync object you do see the side panel as well and it tells you what your output target is and shows you the associated pod with it and of course just like with any other resource you can click in and drill into that panel by clicking the link on that side panel this is an RFE that we had implemented so this allows Kubernetes services to be syncable resources in the event source the event source flow and it also allows Kubernetes resources I'm sorry Kubernetes services to be valid subscribers when either adding a subscription to a channel or adding a trigger to a broker so again just increasing our functionality and that was an RFE going back to the pipeline stuff that Siamic had discussed here is one of the improvements that we now provide a log snippet of failed pipelines they're available in the pipeline run logs so this previously wasn't available so we're exposing it in the logs tab of a pipeline run when that pipeline run is failed we also in the import from GitFlow if there are multiple pipelines that are associated with that runtime we do allow the user to when they opt into adding a pipeline we do allow the user to see the multiple pipelines and select them and as they make those selections that pipeline visualization would change so that they could not only see the name of the pipeline that's offered but also see the tasks that are associated with it so this is a nice again a nice enhancement allowing the developer to kind of understand more of what they're selecting as well as well as being able to have this stuff exposed in the UI which it wasn't previously and then this one is around guiding the user to add web hooks for pipeline updates so previously web hooks had to be handled manually but now when you add a pipeline when going through the import from GitFlow we do generate that tecton trigger for you it's down here on the side panel again there's that copy commands because you would need to copy that URL and go to Git to configure that repo appropriately so again a nice enhancement there okay now I'm going to talk a little bit about export applications so in 4.9 we introduce this export app command which is available with a GitOps primer operator combining this feature with the import multi.caml feature of 4.8 really enables developers to replicate the application in another project in the same cluster or in another cluster what it does is it just provides a zip file of your YAML needed to re-import into to replicate that application but what we've done in 4.10 is introduce some usability improvements for the feature so you can see here we have added the ability to have a link that just says view logs so if you want to watch the progress of your export application that post notification is issued when the user initiates export but if you want you can go look at the logs as it's progressing we also if you have already started an export application and you try that command again we do issue a modal if an export is currently in progress which allows you to either cancel that export restart the export for some reason or view the logs of the current export and then we additionally and this is the same as previously but we do have that post notification issued once that export is completed so that you can download that YAML. Another RFE that we did address in 4.10 is the pod debug mode this is available across the console and at an end dev so it allows you to quickly troubleshoot misbehaving clouds from the UI so if something is a crash if there is a crash looping pod there is a capability of it shows a link to debug that container and brings it to the pod log area and is able to debug that container it allows you to stop that pod from crashing, check environment variables, config variables and also have access to logs and events once you start that container in that interactive shell and last but not least we do have another RFE which is improved quota visibility previously developers weren't able to view their usage their quota usage inside of the console because they weren't privileged so we've now exposed a new area in the project detail page which does allow you to see their usage so you can see the CPU request limit and memory request and memory limit per user here and that's associated with the applied cluster resource quota CR and with that we're going to pop over to dev sandbox and I'm going to give a second to see if Parag is going to present otherwise I will we have a few minutes perfect so the developer sandbox has been upgraded to 4.10 so as you know we keep up with the releases as soon as they go GA so we 4.10 on sandbox for a few weeks now we've added new operators the web terminal operators on it the good ops primer operators are interesting that allows you to export your applications and some of the artifacts into files imported to another cluster so you can take your application setup with you and you go out of the sandbox into a different cluster we also enabled some of the managed services operators on it the latest one being for Roda so now you can use connected databases from the developer sandbox instead of running databases into templates onto your cluster so that's there so that's exciting next slide please and we've added a bunch of when you quick start so one of them being about how to do work as a serverless application so that's there available so folks can enjoy that and next slide please thank you awesome thanks Parag so here's our additional resources we've got blogs and upstream community links as always if you're interested in connecting with us we have a PM mail list devtools-pm at redhat.com or you can connect with any of us individually we also have a Google chat that's available and then finally we do just have a couple of resources stated here too so thanks for joining us and learning more about what's available and how to support that and all of the associated products that we have for our developers thanks everybody