 Hi, everyone. Welcome to What's New in OpenShift 4.14 Developer Project Edition. My name is Balaji Sivas-Supramanian. I run the product for the Developer Tools portfolio, and I'm going to present this edition along with our product managers you see on the screen. Now, before we get started, let's talk about 2024 priorities for Red Hat Developer Tools. It's an exciting year for us in terms of new products and new initiatives that we are able to come to bring to market. We have three big priorities. Number one is developer productivity. How do we help improve developer productivity for lots of engineering organizations that are struggling with it? As they're trying to collaborate across multiple teams, able to share best practices, and be able to deliver software on time. One of the number one thing we're doing here is everything to provide. We're delivering enterprise-grade internal developer portal platform based on backstage.io called the Red Hat Developer Hub, and we're going to continue to focus on delivering that for this year. We also want to differentiate the Developer Hub offering in terms of helping enterprise become more productive with it, with the dynamic plug-ins ability to add plug-ins dynamically, being able to support a large ecosystem of validated plug-ins, as that is one of the key requirements for any developer portals, and be able to have enterprise security, ability to audit, ability to trace, ability to do role-based access control. The other part I want to go and do is that the Developer Tools at Red Hat is to be able to integrate with the value integration to our rest of Red Hat portfolio, including well, Ansible, OpenShift, and other products. Going on to the next topic, our local development. Developers are, again, having difficulty in developing container applications, as well as being able to deploy to Kubernetes. One of the key product that we are addressing in this marketplace is called the Podman Desktop. Podman Desktop has had tremendous success in terms of a completely open-source project and it's available on Podman Desktop website, and you can download it today and you have hundreds of thousands of downloads already happening, and we are able to provide you a first-class ability to build container applications, and also be able to test these applications locally in a Kubernetes, either OpenShift local or in a Kubernetes flavor, and be able to deploy to remote clusters, remote Kubernetes clusters, either it's any Kubernetes flavor clusters or OpenShift. We're also working in our local development is to be able to help developers working with their IDE is to be able to integrate with the Red Hat products through OpenShift integration, serverless integration, and other languages integration, right from their IDE. Last but not the least, I want to briefly touch upon what we announced in the Summit 2023 is around Red Hat focused on providing developers built trusted software. Software supply chain attacks are very large and is a very impactful if some such incidents happen in your environments, and Red Hat is focused on providing you a set of tools to help you secure your software supply chain. One of the other areas that from my team perspective that we'll be focusing on is around, how do you integrate with Red Hat developer hub for all of better developer experience. You can basically go from code building a secure software, being able to build and being able to deliver and being able to collaborate with the rest of our developers in your organization. That's all for now and we'll continue watching and to get updates on specific products from our software product managers. Hi, my name is Brad Baysmore. I'm the product manager for Red Hat developer hub. Really quickly, I wanted to just cover a high level, what is Red Hat developer hub and some exciting announcements about it. So first off, Red Hat developer hub is built on the open source project called Backstage, which was developed at Spotify and it's supposed to allow developers to focus on what they do best, which is coding. So instead of developers being, well, stuck in bureaucratic nightmares, support tickets and documentation graveyards, everything is centralized and managed as part of Backstage. So what is Backstage itself actually? It's made up of five key things, centralized software catalog that keeps track of all of the application ownership, metadata and everything else, such as services, websites, libraries, and then all the other fun jazz. Then plugins, which they extend the functionality and they provide customization. It's a way for you to create a user interface into external applications or internal applications. An example is a plugin for GitHub, so you can see issues related to a item in your software catalog. The next up is software templates or the golden path templates. This is a automation system, a lightweight one that allows you to quickly spin up new projects and standardized toolings and what it really does is it allows you to take your organization's best practices and create a self-service experience for the developers. So let's say they need a new namespace and OpenShift instead of having to file a support ticket and wait for days, they can fill out a software template and the software template will take care of the rest following those best practices, using the already existing automation framework your organization has. The next is TechDocs and this is really as straightforward as it gets. Developers do not like Google Docs or Microsoft Word or all these other WYSIWYG editors that become difficult to maintain through time. So what TechDoc does is the documentation is represented as markdown files that lives in the repository of the resource that the documentation is written about. Backstage then can keep that information in sync and render that information in the UI. And the last tying it all together is search which helps you find the right information across your entire backstage ecosystem. So now documentations, templates, plugins, all of it can be found and centralized through search. And plugins, let's look at that a little bit closer. So with plugins as you can see here in Redhead Developer Hub, there's quite a few that are available right out of the box with Redhead Developer Hub to be packaged. And one of the ones that's really exciting is the topology view from the developer persona in OpenShift. You also have the ability to pull in issues and pull requests, let it be from your GitHub system or GitLab. You also can do CI CD, let it be with Tecton or Argo or whatever it may be. And all these plugins centralize a UI around the resource so the developers don't have to go tracking down 900 different UIs and logins. It's all centralized in one place. So let's look at what actually Redhead Developer Hub is fundamentally. It's a nice little stack here. So at first the top, we have the supported plugin bundle. So these are six plugins that Redhead has developed that Redhead fully offers a 24-7 premium support on. These come with the actual backstage instance, which is also managed by Redhead Developer Hub, fully supported. In the middle there, that little sandwich there is community plugins. So these are the plugins that your community has that you can use. And all of this can run on top of any version of OpenShift and soon EKS, AKS, and GK. To learn more, go to developers.redhead.com slash RHDH. Thank you. Thank you, Brad. Let's talk about Redhead Developer Hub plugins. We just announced the release of Developer Hub version 0.2 in September. This is our last release before GA. In this release, we have had some updates around plugins. More than 20 plugins are now bundled with Developer Hub. So as soon as you install the product, you'll get these plugins right off the bat in the catalog, and you can start using them. These plugins are for various Redhead products, like e-cloak, tecton, the topology view, OpenShift. And they're also plugins created by other developers and third-party companies around their own products, or somebody else's products. Like, for example, Azure DevOps, GitHub Actions. As you can tell, a lot of these plugins you tend to do with DevOps-related products, like JFrog Artifactory for storing container images. So these plugins will work right off the bat when you install Developer Hub version 0.2. The link below will take you to our Janus IDP open-source project where all the plugins that Redhead creates or people create as a part of Janus, they're all published over there. So you can click on the link to take a look at it. Thank you very much. And now I'll pass it on to Stevan. Moving on to Podman Desktop. So the latest version available for Podman Desktop is version 1.4.0. Podman Desktop provides application developers an easy and smooth way to work with containers and Kubernetes on their local workstation. It's available on Windows, Mac, and Linux, and provides a UI to easily interact with containers, with Kubernetes environments, and transition the containers into Kubernetes objects that they can also deploy through Kubernetes environments. In the latest releases, we've been working on improving the compatibility mode with Docker. So now it's easier when you are coming up from Docker to transition from Docker to Podman. You can keep using the same common lines and the same bash script if you have some of them. Compose for the developer who are using Compose, it's now possible to install it directly from Podman Desktop and also to configure it. And you also have a way to manage your Compose group of containers directly from the UI of Podman Desktop. So you can start, stop, restart them from the UI directly. On Kubernetes, so with Podman Desktop, you have the ability to spin up local Kubernetes environment using mini-cube or kind extension. The mini-cube extension has been built by the community recently. And on kind, you now have the ability to show the version of Kubernetes that you want to use to set up your kind clusters. The onboarding is getting improved so that it will more easily configure your Podman environment and get it up running faster as well. The networking configuration is getting a user networking mode to more easily configure VPN configuration in the WSL environment. And for the terminal that are provided inside of Podman Desktop, when you want to SSH directly inside of a container, you now have persistent terminal sessions. And we are also supporting Bash if you have that in your containers. There's a lot of other bug fixes and UI, UX improvements which have been introduced in the latest releases as well. And I invite you to learn more and download the latest version from podman desktop.io website. OpenShift Local. So OpenShift Local, the latest version available is 2.27 and it provides three different presets, OpenShift with the version 4.13.12 Podman presets for those who just want to contain a runtime version 4.4.4 and MicroShift if you want to experiment and get a lightweight OpenShift cluster running on your local environment. There's also a lot of bug fixes that have been introduced around proxy certificates, Windows demands and logs. OpenShift Local is also available from a Podman desktop extension. So directly from Podman desktop, you can set up your OpenShift local environment and use it for development purpose as well on your workstation. So you can spin up a single node cluster or you can also spin up a MicroShift environment to use for development purpose. Reven and Gretel Davatouling, G-Cube version 1.14 is now available. It supports Gradle 8, Elidem, and Spring Boot Layer Jar. There's also work that has been done on improving the support of end charts with end chart YAML fragments. And there is also still the work going on on the G-Cube remote development. Feel free to give it a look. It allows you to run and debug your Java application from a local machine while you are connected to a Kubernetes cluster. So there's demo available and we are looking for feedback. So feel free to reach out with your feedback. You can learn more on the blog post from G-Cube as well to learn all the goodness of the latest releases of G-Cube. For Fabric8, Kubernetes Clients, the version 6.9 is available. The Kubernetes model types have been updated to the version 1.28 as well as the OpenShift model types update to the version 4.13. There's also work which have been done on the Java Generator Gradle plugin and many other things that you can learn more on the different blog posts announcing the releases for the Fabric8 Kubernetes Client. Thank you Mohit. And let's talk about OpenShift dev space next. So we just released a version 3.8 and we are getting ready to release version 3.9 pretty soon in the month of October. What's in 3.8, we focus a lot around improving the experience for developers who want to provide their own personal access tokens for the Git repos like Bitbucket, GitHub, GitLab and saving these tokens in the workspace as a part of the user preferences. So this is something new which makes it easier for developers to provide their own tokens and access these repos. We also made it possible for the DevFile commands which are being known as a part of DevFile, you can actually bring them into VS Code Editor as tasks. So that allows you to kind of, you know, import tasks into VS Code directly by specifying commands in the pattern DevFiles. In version 3.9 that's coming out soon, the key feature there is going to be around the ability to run Podman using KubeDoc within the workspaces of DevSpaces. So this allows you as a developer to now build a container from the code that you're editing in DevSpaces within DevSpaces and then actually run the container there as well. So this way you can do a complete end-to-end development within DevSpaces and don't have to go back to your local desktop and run Docker desktop. It's a key feature and many customers are very excited about this. If you look at the links below there, the admin guys and the user guys and all the documentation are on version 3.8. Let's also talk about the Dev Sandbox for OpenShift. So the new thing is the major enhancements we have made for the developer sandbox is around consoleredhead.com. So in the past we had a landing page in consoleredhead.com for developer sandbox. People could discover it, people could learn about it and then to sign up, it would take them into the developer redhead.com page and then, you know, go through the sign up process there and then they can access the cluster URL from wherever they are. For now onwards, the entire sign up to access experience is actually self-contained within the consoleredhead.com landing page. So you go in there, you discover it, you can learn about it right there and you click on a button, you will get provision right there and once you get provision, you'll get access buttons to launch specific parts of the technologies and the platforms that are enabled within developer sandbox. So you'll be able to access OpenShift directly, access DevSpaces, access to the roads, to better notebooks capability. So this way from a landing page, you can pick and choose which platform you want to experiment with and play around with. So very exciting feature and we are going to be enhancing even further. This is the first step for us to get it in consoleredhead.com. Hello everyone. Welcome to What's New in OpenShift 4.14 Developer Edition. I'm Mohath Suman and I'm the PM for IDE Tooling. And today I'll be taking you what enhancements we did with respect to the new features around multiple extensions we have for Visual Studio Code, IntelliJ and Eclipse. So let's get started. Let's start with OpenShift extension we have for VS Code IntelliJ. We did tons of improvements around OpenShift extension, a lot of bug fixes, a lot of enhancements and most importantly we came up with multiple new workflows which allows developers to quickly get their apps on running on OpenShift. We got a good feedback from the solution architect communities and some of the developer sessions we did at multiple conferences. So right now with OpenShift extension running on VS Code and IntelliJ, so there are three different workflows which the developer can do. One of them is to deploy their applications on top of any hybrid cloud running OpenShift. That can be OpenShift running locally, OpenShift running on Dev Sandbox or OpenShift running on Azure, OpenShift running on AWS. So any version of OpenShift is supported directly from this extension. The best part here is the users will get a dedicated workflow where they can deploy their applications in three different ways. Either they can deploy their apps running from a local workspace which is already open in their editor. They can also deploy their applications which is present in a remote grid repository and third they can also deploy their applications starting from a starter template project using Devfiles. So these are a major improvement what we did, simplifying the overall workflow. The second important stuff we did was we made sure the integration of help into the OpenShift extension is very smooth. So right now users can browse and install any help chat available on the cluster. So that way developers will have a choice to work with different workflows around Devfiles, around help charts and other scenarios just being within their editor itself. The third major improvement we did was we integrated OpenShift serverless functions directly into the ID workflow of OpenShift. So now developers can run their functions, manage their functions, build their functions directly from the OpenShift extension. Previously we used to have a dedicated K-native extension available on the marketplace but now we have integrated the OpenShift serverless into the OpenShift extension also. So that way it provides a unified experience around anything OpenShift. So these are some of the major improvements what we did for the OpenShift toolkit extension and we are going to do a lot of enhancements down the line with respect to how you can deploy your applications on Podman, how easy it becomes to create your applications, debug your application and directly deploy with one click directly on a Podman running. It also integrates very well with Podman desktop and the best part is it allows you to give you a recommendation based on your workspace open. So let's say your workspace already has a Java application open. So the extension will prompt you a dedicated Java starter project or a Java dev file that how to configure the environment variables, how to set up the networking and other stuff directly from your ID. So that way the overall simplification of the entire workflow is smooth. Let's go ahead and see what we did for the other extensions we have in our portfolio. With respect to the server-connected extension which we have for Visual Studio Code and IntelliJ, the major improvement what we did, whatever functionality which was available on Jba Stools on the Eclipse platform is now also available on the Visual Studio Code and IntelliJ. So the customers or users who were used to running EAP, Wildfly directly on an Eclipse platform can still run those middleware runtimes from VS Code IntelliJ and they're actively improving the workflow of running EAP and Wildfly on VS Code and this extension is also available on OpenVSX Registry, which means that it can be very easily installed on Red Hat Dev spaces. So that's one of the major improvements what we did for OpenShift 4.40. Now, one of the important workflows around IntelliJ was we have improved a lot around the Kubernetes plugin we have for IntelliJ. We did 1.0 release for IntelliJ Kubernetes. We are getting good community attraction around it and we are improving a lot of functionalities because it's also a dependency for the OpenShift plugin we have for Kubernetes. We have improved the Kube config workflow. We have improved the init containers for logs and terminals and now users can quickly scan through the different logs they have they're running on our Kubernetes cluster, how multiple terminals, which allows them to see the error logs or allow them to see what configurations have changed and also inspect the detailed connections what they have for special build config, deployment configs connected to the cluster. As I already mentioned, the serverless functions workflow is now migrated to the OpenShift toolkit extension. So that way we are trying to make the unified experience there. Down the line, we'll also try to see if we can integrate OpenShift pipelines into it so that the entire OpenShift workflow will be there in one dedicated extension. Let's go ahead and see what we have improved on the language part of the ID tooling. With the Visual Studio Code Java extension, we are reaching around 30 million installs which is a very magnificent feat because that's the number one downloaded extension available on VS Code Marketplace. We are also coming out with support of Java 21 down the line. So that's very exciting. Coming out from Java 8 to Java 21, that's something which the customers are looking forward to with respect to Java development. We have done a lot of improvements, feature enhancements and performance improvements with respect to VS Code Java, such as JTK detection on the local machine, improving the graded application and also the code completion, document refactoring. So those certain small features on the VS Code Java is done and we are trying to make sure we release every month. With respect to the Quarkus plugin we have for IntelliJ. We have done terms of releases down the line. We have improved a lot of functionality. So the feature-wise, the Quarkus plugin on VS Code and Quarkus plugin on IntelliJ are slowly coming at the same level. We have the Quarkus 3 support out there. We have a very improved support for Qtemplates and even the language server parser which is there for Quarkus is improved. And this is overall improving the developer experience around the whole Quarkus community we have and we're going to enhance a lot on the IntelliJ Quarkus plugin down the line. With respect to the VS Code YAML extension we are reaching around 14 million installs. We have done a lot of improvements around some of the violations for IPv4, VSx and also improving the schema definition for the YAML files. So VS Code YAML is used as a dependency for multiple ID extensions for various companies and this acts as a very strong point when we are configuring any configuration for YAMLs. So these are some of the enhancements what we did with the overall ID tooling. We are going to improve a lot down the line and we are actively doing releases every three weeks. So feel free to get in touch with us if you need any specific requirement or feature set and thank you for your time. See you. Let's talk about the developer experience enhancements in OpenShift console. So the developer perspective in OpenShift web console was enhanced in version 4.14 with some key capabilities around our layered products like serverless and pipelines. One of the key ones is they can now actually test serverless functions directly inside the console. So you just, you know, you create the function code and click on test button, you can run it right there and you can test it before you even push it into Git. There are some new quick starts now. They also allow you to discover it had tools that cryo style operator and also the experience for the pipelines UI in the developer perspective has been and the admin perspective has been enhanced. So these are some of the key enhancements in 4.14. We have some more exciting features coming along the way in 4.15 we should talk about later on. So to conclude with everything we presented, we hope that you're excited about all these new enhancements that we have delivered for OpenShift 4.14 for all parts of the developer portfolio. For developer hub, it's one of our key products. If you want to take a look at the dev preview today, you can go into developer hub on the link right here and can apply for it. And once it's approved, you can actually download the image and run it on your own cluster of choice. Podman desktop is an open source project, very popular. You know, as Devon mentions about creating containers and making them around Kubernetes directly from your desktop, it's targeted for application developers. Go to the link below and you can download it right away and get going with it. Developer Sandbox, always on. Free to use, no setup required. Just click on the button, get signed up immediately, get access to an OpenShift cluster running live, you get a private environment in it, you get enough resources and preconfigure developer tools to just get going without having to do, you know, without having to install or even pay for OpenShift. And lastly, the developer redhead.com program. If you come in here, if you register for this, if you join our program, you get access to amazing content, including the ability to download. A lot of the products that we have, get the ability to bring in, you know, eBooks, to bring in like learning materials. It's a great program, a lot of free assets available. All you have to do is just click on, it's a free subscription, you can sign up for it. Thank you very much. I hope you found the content useful and see you next time. Cheers.