 Hey, my name is Cedric Laiber and I'm an intern on the Red Hat OpenShift Developer Advocate team. And I'd like to explain how you can get started using OpenShift Do or ODO to deploy an application on OpenShift. Now, ODO is a fast, iterative, and straightforward CLI tools for developers like you who write, build, and deploy applications on Kubernetes and OpenShift. What I love about it is the simple syntax, official support for Node.js and Java, and the fact that it's completely client-based so you really don't need anything other than your Kubernetes or OpenShift Cluster to start working. Now, today we're going to deploy an application using ODO 2.0 and give you a little introduction to something called a dev file. So, what's a dev file, you might ask? Well, that's a great question. A dev file is a portable file that describes your development environment, things like a container, predefined commands, and a pre-roject to initially clone. ODO is the tool to take this raw dev file and transform it into a workspace for any number of Kubernetes or OpenShift clusters. Today, we're going to be deploying our first dev file with ODO and deploying a Node.js component to our OpenShift cluster. Now, before we begin, there's a few things you'll need to get started. Firstly, since ODO is a client-based tool, you'll need a Kubernetes or OpenShift cluster. We'll be using a standard OpenShift cluster today, but keep in mind all of these commands are almost the exact same if you're running on a MiniCube cluster. If you haven't already, download the latest version of ODO, which can vary depending on your operating system. Feel free to go to odo.dev for the most recent instructions. Since I'm on macOS, I can easily install ODO with two simple commands. In addition, there's various core components such as projects and components that we'll be going over during this demo. Now, we'll be deploying a sample Node.js application that uses Express and NPM for a demonstration, and it starts with downloading the Node.js component. Once we clone that example repository in our local directory, we can switch to the folder and start working. Now let's create a new project with ODO Project Create in the name of your project. Before we start to deploy our application, let's list all the available DevFile components with the command ODO CatalogListComponents. We'll be using the Node.js component that you see right there for our application, and let's create a new configuration using the ODO Create command. The ODO Create command specifies that we're creating a local configuration that will be used to track how you want your code to be deployed. The first argument is, of course, the language, which we have the option of Java Maven, Quarkus, Spring Boot, and even Node.js. The second argument will be the name of the application that you're deploying, and for us, we can use something like my Node.js or example, perhaps. You'll notice that once you run the command, the DevFile is checked for compatibility and created from the default DevFile registry before finally being validated. Great! Now to be able to expose our deployed content, we need to create a URL to expose the component to the outside world. With the ODO URL Create command, we can define a local URL to access our deployed content once it's live. If you're on Minicube, there will be different instructions that allow you to use your ingress domain name to create the same accessible URL. We're now ready to deploy our code out on the OpenShift cluster, and the ODO Push command can help us do just that. Once ODO Push completes, which may take a bit of time, your source code is actually going to be running on a container in your cluster. In addition, you can use the ODO Push command to quickly change and redeploy source code in your cluster. If you have access to the OpenShift web console, you can change to the developer view, switch to the new project that you've made, which for me is my project, and you'll now notice that there's a new Node.js pod running, as well as an open URL link, which allows direct access to the application that we've built. If you'd like, feel free to navigate to the pod and select the logs header, which will show you the logs of the pod like npm start, and whenever the application is accessed. Now let's find the URL of our component with the command ODO URL list, which will list the name of our component, as well as the accessible web URL to access the application. I'm going to use the curl command to quickly see our deployed application running, and you'll notice we see default output from the running Node application inside of the console. Looks awesome, and in addition, you can visit the URL in a browser and see the same output. If you'd like to delete your deployed application, you can run the ODO delete command on the currently open component, which for me is my Node.js. Thanks so much for watching. If you're interested in or have any questions about this video, please feel free to head over to developer.redhat.com or odo.dev, where we have plenty of resources to help you learn more about ODO, OpenShift, and more. My name is Cedric Labrin, have a great day.