 Good morning evening afternoon wherever you are and welcome to the what's new and OpenShift 4.13 developer tools edition Today we do have Brad, Parag, Rob, Stefan, Mohit, Kasturi, Serena and myself, Markus talking you through the latest editions that are exciting and coming up for OpenShift 4.13 So thank you so much for watching and as usual this is a recording if you have Anything that you want us to know, please feel free to comment in the video or reach out to us contact information Will be at the very end of this video enjoy take it away In developer tools our mission is to help developers improve their productivity Agility and the security with which they can deliver applications as quickly as possible to meet the business needs In 2023, we are going to focus on three key areas onboarding to help developers get going with the solution stack of the companies as quickly as possible Local development so that the agility can be increased and they can go from experimentation to quick rapid feedback loops and Working with the you know the end deployment targets directly from the local development environments and lastly with cloud hosted services Delivering cloud hosted services that help with the end to end delivery of the application securely and also integration with cloud hosted services You know from other areas of our portfolio So in the next few slides, we're going to share about the progress we have made and our plans and what's new with OpenShift 4.13 in these areas Hi everybody Let's talk about OpenShift are special and what's new in the product since 4.12 Dev spaces run quite a lot And they progress very well since we spoke last And we have been working with our customers and developing a roadmap and to that end Dev spaces intends to make its products simpler faster and as cloud native in every release as possible To that end here are some major and noteworthy enhancements since 4.12 release We will support 4.13 in one of our future releases Customers have been asking us to make a pre-release version a beta version so they could kind of test it Before they use it on production and we have made that possible And now Dev spaces allows installation of pre-release versions or beta version for testing purpose only PS code is now the default editor We have faded eclipsed there as an editor and are working to get production ready support for IntelliJ Customers can also now do apartment build from within the containers This has been one of our key asks from most of the customer and if we made it possible in our One of the releases we also have support for workload identity federation We also have added support for Azure DevOps Git servers in addition to our existing github github and bitpocket There are much more smaller enhancements in the product and the details of which is available in the release notes of every version The whose links are provided in the same deck You can also refer to our documentation for additional details. Thank you for listening in Hello, everyone Welcome to what's new in open chat 4.13 developer vision around ID extensions and Odo CLI 2 I am Mohath Suman. I work as a senior product manager working at the that getting to the developer experience around offerings for multiple ID extensions for vision studio code in deli j and it keeps tooling So let's get started what we have new for the open chat 4.13 The first one is we have OpenShift toolkit which is an ID extension for vision studio code in deli j Looking around creating debugging and deploying applications directly on top of OpenShift So this is the Go-to extension if you want to work with any application development get into OpenShift or any Kubernetes cluster running on hybrid cloud OpenShift on AWS, OpenShift on Azure Or even OpenShift running locally on a laptop The support for OpenShift toolkit is provided for windows linux and macOS which is specific to any arm support from Mac Intel based also extension is available for vision studio code marketplace Jetbrince marketplace for Intel eJ add even an open vsx registries So that users can also install the OpenShift extension on their running dev spaces With respect to application development, there are multiple features what we have added for the release and what's new So one of the important factors what we have added is now users can Browse and also install Helm charts on their clusters directly from the ID So they don't have to leave their ID to browse and install Helm charts Everything can be done directly from the OpenShift toolkit extension The other important aspect what we have improved is whatever workspace you have already in your vs code instance and you want to deploy that Application on top of a connected OpenShift cluster So the extension will automatically detect what type of application it is and it will also recommend you Based on that detection what type of configuration files are needed. Basically what type of dev file is needed So let's say you have a dot net application opened up in a workspace and you want to deploy that dot net application The extension will automatically detect it and will recommend you that specific dev file Users will have a choice to use the recommended dev file or even provide their own dev file if they already have a specific dev file which they were working in the past One new feature which we have added on the OpenShift toolkit side is right now users can Work with application development deployment and even debugging on top of any cube of the OpenShift cluster But now you can also do the same work so directly on a running part my instance So let's say you want to deploy or debug an application on a container base Workflow on top of part man. So you can do the same through the OpenShift toolkit. So it now supports part man also Under the hood OpenShift toolkit uses Odo CLI So we have the support of the latest Odo CLI C dot 9 dot 0 With respect to what type of cluster users can provision from the ID itself So we have made an attempt for the users who do not have Access to a dedicated OpenShift cluster They can provision an OpenShift cluster directly from the ID without leaving your ID That can done in multiple ways. You can also provision OpenShift running locally using OpenShift local Or you can provision a developer sandbox engine, which is valid for 30 days free of cost directly from your ID In the multiple releases what we have done in this quarter We have improved the support of developer sandbox. So now users will need very few clicks And they will quickly bootstrap their developer sandbox running One of the important improvements right now what we have done based on the multiple requests coming from the community And even from customers to run the OpenShift toolkit in a disconnected environment So now you can run this extension in a disconnected environment and leverage all the features what we have with respect to Deploying your application or even deploying your application on top of the connected OpenShift cluster Let's move on to the different set of ID extensions what we have We have multiple ID extensions getting to multiple products from Red Hat One of them is OpenShift toolkit as I discussed the multiple releases what we have done the latest one is 1.3.0 And we have improved workflow for provisioning a developer sandbox cluster even support of help that is Intuitive to the developer experience and support of podman is provided in bed to the extension right now The other extension what we currently have improved and added multiple support is the server connector extension So this extension basically allows users to work with their middleware runtimes It has support of wide flight 24. It has the latest support of eap 8 And it's also available on open v6 registry. So for the users or customers who want to work with Middleware runtimes on top of depth spaces they can also install the server connector extension directly from the open v6 registries and All the workflows will be supported there Coming to the other extension what we have is getting to the Kubernetes extension on IntelliJ We have received multiple feedbacks and multiple requests based on the workflow of how Kubernetes extensions should behave on IntelliJ As to this extension also a dependency for running OpenShift extension running k-native extension and Tekken extension So we have added multiple features like the support of kube config files from any location just not the default one It also supports multi resource files And we have also improved the error management in the kuben extension So now users can inspect the details of the connection errors and other workflows Coming to the serverless extension We have the k-native extension which is available on for vscode and IntelliJ The important improvements what we have done is we have improved the support of Building and running or deploying the functions directly from your id So now the view of the serverless function will give you what state the function is currently running Is it running in a build state? Is it running in a run state or is it in a deployment state? And it also give you multiple error management workflow that okay on what state that function has failed And it will allow you to create multiple functions together It supports S2I built-in images right now and it also supports on-bit clusters everything with respect to Serverless functions can be directly done from your vscode and IntelliJ id So you as a user will never have to leave that id and you can work everything seamlessly from your serverless functions Let's move on to what we have with respect to id extensions for specific languages like java quartet yaml vscode java stands out as the number one downloaded extension supported by red hat We have approximately 24 million installs With respect to the latest version what we released last week with 1.18.0 We have done multiple bugs fixes multiple enhancements some the prominence one are It's now provides java 20 support. We just should report java extension it has improved non-box support and also the Gradle annotation processing is that multiple code completion and documentary factoring are added into that extension and Coming to the quarters extension the latest Release is 1.13.0. One of the major improvements what we did for quarkus for this release is we now support quarkus 3 out of the box The last one is vscode yaml yaml is an extension which is a dependency for The propensity extension the Kubernetes extension for the tecton extension as a function extension And it has approximated 12 million installs and we have improved multiple bug fixes and even multiple enhancements One of them is improved ipv4 and ipv6 validation and also improves schema definition and solutions for the specific analytics So these are some of the improvements what we have done on the space of id extension Both vscode java and eclipsed tooling The idea is to make sure we do consistent releases based on the feedback coming from the upstream community and also based on the release of openshift 4.3 So I have mentioned the specific link for the marketplace the github repositories and a changelog with the specific releases So feel free to look at it and if you have specific Feedback do reach us out and we will be happy to take care of the multiple feature requests and enhancements So let's go to the another tool what we have for developer experience around openshift that is known as odo Odo 3.9.0 is now available for windows linux and macOS and for mac it supports ARM architecture also One of the important improvements what we have done for odo right now is we now support odo in a disconnected environment So there was a feedback which came from the community that odo should allow to debug Deploy or create applications on top of openshift which is running on disconnected environment So that workflow is now supported out of the box using odo cli Uh odo in i right now integrates very seamlessly with the id extensions So id extensions under the hood run odo commands and whatever workflow which is there on odo 3.9.0 is By default link to the id extensions A few features which we have improved in this release of odo support security animation support for the kubernetes and openshift clusters We have the demo video already uploaded on youtube feel free to have a look at it and understand it more We also now have support for auto build and deploy by default depth file fields So idea is to make sure that whatever new fields which are added In your depth file configuration the odo should support it by default and in this release We wanted to make sure the auto build and deploy by default depth file fields Should work out of the box. We have a dedicated demo for it on youtube. So feel free to work around it One of the very important factors with respect to odo right now is If you want to work with any application which you want to deploy on top of openshift Auto right now automatically analyzes what type of application it is it automatically detects an application and recommends you the specific depth file needed for it And they also recommend you the specific port which Application needs to run so it basically improves the experience for developers who wants to deploy their application using the odo cli on top of our running openshift cluster The other important improvement right now is for the previous releases odo support for podman was an experimental mode But with odo 3.9.0 We have made sure that odo on podman is out of experimental mode Which basically means that any command which you want to run on odo n8 odo dev or debug Any specific odo command which you want to deploy that application on top of podman cluster Will work seamlessly this release has multiple bug fixes and multiple workflow improvements And we are targeting to make sure that we keep on improving those supports So that users who want to work with anything related to openshift application development Odo should be the go-to tool for them We have multiple blog posts, which is available with respect to what features are added and the specific releases what new improvements are added We have also added a quick start guide with respect to how you can work with any dot net application development Or a Node.js application development or a Java application development using odo cli And on redhead developer we have a dedicated cheat sheet for odo where We have mentioned that how specific commands of odo such as odo init or odo dev or odo debug will work And how the functionalities are linked together For application development on openshift or any kubernetes cluster running on habit cloud If you want to reach out to the team the team is present on the kubernetes upstream Slack channel and the channel name is hash odo So reach out to the team for any feature request or any enhancements and we'll be really glad to make sure that we Keep up to their respects on priority So this is what we have with respect to what's new for odo on openshift 4.13 And whatever demo videos will be uploaded on youtube. So feel free to look at it and provide your Valuable feedback. So that's it for my time. Thank you for listening Hi, my name is brad I'm the product manager of the redhead developer sandbox And today i'm excited to give you an update on several of the things that we've been working on to make the developer sandbox The best experience for developers on openshift First thing I do want to say that we will be updating to 4.13 Of openshift on a fast track schedule Expect to see an announcement about that inside of the application Now speaking of inside of the application, let's talk about this new experience that we've been working on to help make developers As successful as possible First up Is the help center This is the centerpiece of everything that we've been working on for the past couple of months to make developers as successful as possible By bringing all of the content that redhead has been creating from learning to labs to activities Right here inside of the application and a lot more You'll notice several sections inside of the help center Which can be activated by a small blue question mark in the bottom right hand corner no matter where you are in the sandbox You'll notice how to's Community sharing your feedback and reporting a bug. So let's go through all of these right now and let's start with how to The how to is a place where you can see all of the content that red hat has made To experience everything from just getting started to some of the most advanced concepts in openshift Such as how to implement natural language processing inside of openshift with jupiter notebooks You can search to find what you're looking for And a guide will pop up to walk you through whatever that material may be and redirect you to the right location In this case, it's going to send you over to our activities where it's going to show you how to use TensorFlow and jupiter notebooks And the developer sandbox to do some natural language processing Next up is an example of one of those that is exporting your sandbox This now enables you to take the applications you have and send them To another openshift cluster now This is still very early on and requires some manual work But this in-app guide will walk you through the entire process on how to take the completed export that's generated here And import it into another openshift cluster such as rosa We're really excited to see where this goes forward Now as you're working on these different things you might have some thoughts And they might have some problems So now we have a way for you to report bugs inside of the application Simply click report bug in the help center and a form is going to appear From here, you could fill out a summary of what that bug might be You can add your email address which we need to use so we can contact you about the bug And this is the email address you use to sign up with developer sandbox Then add a description This form will then now automatically create a Jira ticket In our new public developer sandbox bug repository Now I said public because we believe in collaboration and openness And so this is a way for you As developers or anybody else to help collaborate with the developer sandbox team on addressing any of these bugs Once you hit submit you'll be taken to this page here. Simply click login Using the same red hat login that you use for sandbox You'll be sent to this form where you can add more information if you need or simply click create You'll notice some information that's been added to the description That is information that helps the team diagnose the problem and identify the specific account you're looking at You can also click in and see the other bugs You can leave comments and monitor the status We'll do the best we can to address your bugs as quickly as possible Now you might have something that's not a bug It might be an idea or a feature request And that's where our new feedback experience comes in Simply click on the question mark and click on share your feedback From here you can share any ideas that you have feature requests or things you'd like to see better More excitingly we have an entire portal experience for this to create a collaborative environment for you Here you can submit any new ideas, but you can also see what others have submitted You can go in Upvote them and download them to help us as the team know what matters You can even leave comments for us and communicate back and forth And you can see at the top or request status We'll let you know whether or not we're going to build this you put it on the roadmap or something We're not going to do Off to the side you can see things we released and what's coming up on our roadmap Because red hat is an open culture And we believe that everything we do for sandbox should be open and transparent in a collaborative way And this new feedback experience, which will have more information soon Enables you and developers to do that anyone is welcome to share their feedback and see what's going on next That about wraps it up for me. Thank you very much Hi, hall. My name is stevan lemur and I will cover our maven java tooling as well as pulmon desktop and open shift local so for Our maven and gradle java java tooling. We have g cube G cube version 1.12 is now available One of the biggest features that we have been releasing is the ability to do remote development So it is a new feature that allows you to run and debug your java application from your local machine While connect to a kubernetes cluster. So it's It's essentially like placing your your local developer machine inside your cluster So it's available in preview and there is a demo that is available if you want to play Around with the capabilities and see how it works, which is available As well on the link in the slide We also add the support for corn job controller Generation as well as setting resource limits and init containers through xml and dsl configuration There's a bunch of bug fixes and other improvements And I invite you to read the blog post to learn more about the new capabilities that have been added to to gq The fabricate kubernetes clients the latest version available is the version 6.5 um The kubernetes model types has been a have been updated to uh the version 1.26 We also added the support for Pod with fmrl container operation as well as uh java types for customized APIs You can learn more about the different new capabilities and bug fixed in this in this version In the blog post link in the in the slide as well So podman desktop podman desktop, uh, if you are not aware about what it is yet it is A desktop application that allows you to easily work with containers and kubernetes It is even better when you are targeting to run those containers on open shift Um, so it provides a bunch of capabilities to get podman and prepare the test open shift local getting installed and kept up to date you can interact with containers You can interact with pods it has It has capabilities also to handle vpn and proxy configuration as well as managing the different image registers But uh, you you you may be uh connect to And it also provides a airgap installation for for some of our Users who might be interested by this installation procedure The latest key updates is that we added the support for for For docker compatibility mode. So that means that when you start podman desktop You have the compatibility mode with docker which is enabled out of the box you can then Use podman as your default container online But all your different docker commands as well as the different tools that communicate with docker will just Work with uh with podman You also have the ability to Podify your containers so that's the ability to choose certain containers that you want to Bendle together as a pod and to run together as a single unit As a pod so you can do that from podman desktop You have the ability to generate the kubernetes Yammer's for containers and pod and you also have the ability to directly deploy To a kubernetes environment. So from podman desktop you have the ability to Choose your kube context to select To select it from the tray menu of of podman desktop And then inside of the ui you will connect to that environment and you will be able to do your Your deployment directly From from the ui So air gap installation has been added As well As i mentioned earlier And you also have the compose installation which is available directly from the grid. So if you want To Work with compose Podman desktop allows you to install compose and to directly configure it to run with podman as a container container engine We recently added the an extension for kind so you can install create and manage kind cluster directly from podman desktop And those kind clusters are going to run in podman and you can deploy To kind and share images from podman directly to kind. So this is very convenient when you want to Work with the containers and test them in the context of kubernetes and there's a bunch of bug fixes I really invite you to To to learn more about it on the websites podman desktop.io there's release notes and There's all the different downloads that are available from from there So open chief local previously known as kubernetes containers So the version 2.17.9 is now available There's three different presets. So if three different environments that you can set up from your local developer environment You can either have a single note open chief cluster and it will provide open shift 4.12.9 Or you can also have podman podman 4.1 And we recently introduced a micro shift as an experiment to provide you a lightweight Cluster that you can use to test your your application onto a An open shift environment Which will run locally And with that I am ending over to rob My name is rob gormley and I am one of the product managers for helm on open shift As you know, helm is one of the most popular package managers for kubernetes And we continue to integrate its capabilities across open shift The goal is to provide an integrated developer experience that enables self service communication Different services that would be consumed by the application developer By also minimizing the need to interact with cluster operators and improving that entire developer workflow Open shift 4.13 is largely a maintenance release for helm upgrading from pre dot 10.1 to pre dot 11.1 In open shift 4.13 build doesn't see a lot of visible changes But under the hood a lot of work has been done to improve the security performance and reliability of the product We've been working ensuring that our package jenkins image stays up to date with the latest security and bug fixes To help ensure that your jenkins experience remains optimal While under the hood we've been removing legacy artifacts codes and agents to both optimize this code base As well as reduce the security footprint You'll notice that we've removed code that supported red hat enterprise linux 7 as well as a maven and no j s agents Which are no longer supportive Hi, everybody My name is serena cakeley and i'm the product manager for open shift developer console as well as The backstage offerings in the future So let's talk a little bit about the developer experience in open shift As usual, we have a lot of improvements and enhancements to share with you today about what's coming in open shift 4.13 First, let's chat about console customization We often hear from customers that they want to tailor the console experience for their developers Over the past few releases. We've been enhancing that experience for cluster admins in 4.13 We've added another customization capability through our form-based customization experience admins can now change the default Pre-pins navigation items in the developer perspective This can be accomplished by going to the cluster settings in the administration navigation area clicking on console configuration Then go to the customize Action from the actions menu and go to the developer tab on that page to start customizing What resources you want your developers to be able to access most frequently from the developer perspective? Another area that we've added some enhancements is in The helm area. We've done a couple of things here. We've updated some helm terminology Instead of saying install and uninstall uninstall helm chart We've now changed that to create and delete helm releases because that's what you're actually creating And we've also made some updates in the create update and deletion process Those those flows are now performed Asynchronously so you're not making you're not waiting for those to complete before you can go on to your next task Another enhancement that we've looked at or have heard requested is for the ability to easily identify Which pods are receiving traffic in the console? developers and admins alike Now have the easy ability to view whether or not a pod is receiving traffic In the topology view on my lower left hand screenshot You can see the resources tab of topology now displays an icon Dedicating whether the associated pods are receiving traffic And on the right screenshot you can see that when you navigate to the pods list view Users are able to manage the default columns of their pods list view and display the receiving traffic column for easy access to that information Now let's move on to the web terminal As you know when the web terminal operator is installed users have the option to instantiate their own web terminal Getting access to easy Easily issue cli's from the console Now when you invoke your web terminal users have the option to customize their own version Whether that be to customize the timeout period or even utilize their own image in that terminal Which could it be able to extend the cli capabilities from within that web uh web terminal instance Moving on to serverless when the open shift serverless operator is installed workloads are um workloads are now Have the ability let's stop that moving on to serverless When the open shift serverless operator is installed Developers now have the ability to create serverless functions They can do that either from the create serverless function item on the ad page Or through the import from the get flow This now supports two different flows. You can either Create serverless functions through builder images or through a tecton pipeline if you happen to have open shift pipelines installed as well Let's move on to open shift pipelines when the open shift Pipeline operator is installed as you know, we have a great user experience around pipelines. We've enhanced this a little bit more In two major areas One is when you do an import from the get Developers are able to configure their pipelines as code repo through that single process So eliminating its two-step process and making it a single flow. So more efficient process Is it results? Additionally, there's some improvements that have been made to the overall experience when dealing with pipeline runs improvements to navigation as well as exposing task run Duration more consistently throughout the application Okay, let's talk a little bit about project Janus and backstage in october of last year red hat joined the backstage.io community One of the leading open source idp projects Onboarding and developer productivity is a huge problem for our customers and idps and backstage can help solve these problems So where's red hat investing? We're investing in the upstream backstage community We started by contributing a home chart to improve the initial installation experience at backstage But we're also contributing to backstage core We're looking here to see how we can bring in dynamic plugins to the community and see if that will help solve one of the Underlying problems that platform engineers have today with maintaining backstage We've also started a new open source community called janus. This is our red hat sponsored community for building internal developer portal Alongside alongside backstage here. We're curating best practices custom actions collaborating with customers on plugins Working on a more focused home chart for open shift installations as well as providing some sample golden path templates That we know our customers and upstream users are actually looking for We've also created a showcase application which i'll deep it dive into in a bit Finally, we are working towards the product product supported products What we just hear in the coming months is about our Productization efforts around a red hat build and distribution of backstage core as well as a set of red hat supported plugins But for now if you're interested Please go to our showcase application or our gate repo and take a look at what we have available in our janus showcase I'm going to do a quick little demo here This is again showing you what jana showcase application looks like a single pane of glass For a developer or any persona to see all the tools that they're utilizing and what they need to access If they go into a catalog, they're able to see all of the services that are available Here is going to show the backstage showcase application that i'm working on right now As a product manager what i love about this is i'm able to quickly identify the issues that are associated with this application I can also see what prs have been merged So if the developer tells me yesterday that something's been fixed and i come in today and i don't see it yet I'm able to quickly see from inside the backstage showcase from the inside backstage portal If that pr has been merged or not In addition to that we've got some great plugins available already We've got our topology plugin Which looks very similar to what we have an open shift developer perspective inside of the open shift console Except it's read only we have the ability to see Workloads how they're connected as well as the detail kubernetes details as well as associated resources that those workloads have We also have a quay plugin which allows us to look at the images from that quay repository And get some information of them Specifically the security scan and you can even deep dive into that and see if there's vulnerabilities associated with those and if so you can take a look at those security advisories Outside of the backstage portal, but again i'm able to access all of that from inside of backstage Showing the great aggregation of data from within a single pane of glass We've got some things like open shift learning paths So if you have a developer who's learning open shift instead of having to find where they can access those learning paths We've pulled them right into the jana showcase application We also have a multi cluster plugin which works with Open cluster management So i'm sorry the open cluster manager So if you have clusters that are using the multi cluster hub from there You're able to drill into any of these clusters and kind of take a look and see what the status of them are Let me switch to another one I can go into let's see if I this one will work I come into the status of the infra cluster and i'm able to see that the open shift version is 4 10 26 But there's an upgrade available. I can get access to my console url I can see how many cores memory size number of pods are available, etc But this again provides a great way for developers or cluster admins in this case Even to get a nice view of everything from within a single pane of glass And if they need to go do something outside, they've got a quick link for access to do so Another thing I didn't mention was we also have an argo plugin So we have the ability to inside of let's see my overview I'm able to quickly get an overview of the argo cv status seeing that it's synced and healthy Now i'm just going to quickly jump over to the create page Which is where we have our golden path templates golden path templates are away for platform engineers to provide self-service to their developers In this case, we have a number of them for onboarding brand new applications these this type of Golden path template can make savings from for your developers for something that used to take Seven to ten days to a minute or more What one of these will do is it will allow you to um a developer to come in with some guardrails Provide some options and information around what their github organization is what they want the project name to be called Do they want to use in this case tecton or do they want to use um GitHub actions and also if they want to store their image in the open shift internal registry or on quay And once they're completed with this flow, what happens is the system will go create that github repo add some sample code dot net code It will add that ci. So the get the tecton pipeline to it It will build and deploy that and then it will have that whole thing managed by argo. So Things are created all your applications are created consistently securely and with guardrails for a developer so um That's about what we have today for a Early look at what we're doing with both of the backstage and janus and our productization Futures, so keep your eyes on what we're doing in the janus community and we'll look forward to Seeing the next quarter with more updates. Thank you Thank you serena. I guess now it's time to wrap this session up quickly Um, I want to want to briefly dive into the additional resources available Our upstream communities as you know and love them Make sure to check in with janus dash idp.io and potman dash desktop.io in particular reach out to us There's a chat. There is a pm mailing list that you can reach out to Um, also don't forget to register for redhead summit may 23rd to 25th in boston There's a ton of sessions hands-on labs materials stuff to learn So don't miss out on registering for that event If you haven't sign up for the redhead developer sandbox because you get to play around with your own sandbox play with containers start exploring open shift That is definitely something if you haven't done so, please make sure to register In general just join the redhead developers program if you want to know more and I'll leave you with that. So thank you for your attention today and hope to see you soon. Bye. Bye