 Hi, in this video, I will show you three different ways of deploying your app on the developer sandbox for Red Hat OpenShift. Are you ready? Okay, let's go. So here I'm on my Red Hat OpenShift sandbox. It's empty for now. I haven't deployed anything. And I'm on the developer perspective because I'm a developer. And there are different ways of adding your application to this sandbox. Today I'm going to show you three different ways. We will see how to use directly a container, how to use a get repo and finally we will see how we can upload a jar file directly. Let's start with the first one, a container image. So this is if you master the concept of containers. You know how to craft your own Docker file. You know how to do a Docker push or you know how to use Podman or you know how to use Jib. Anyway, you have your container image and now you want to deploy it. So let's try out this option. I click here and as you can see I am on the screen where there's one really important thing to fill in is the location of my container image, of course. So for me it's located on quay.io, that's the registry from Red Hat, Sebastian Blanc is my username, zero slash and my container image is called hello sandbox. There's some validation happening. It's validated awesome. And now I can change the icon of my app, okay, that's just visual but it's nice. The name of my application, let's call it hello sandbox container and then I can choose the type of resource that I want. In this case I want a regular deployment. My deployment will create my replica set and will create my pods because remember OpenShift in the end is Kubernetes, okay. I could go for deployment config which is more specific for OpenShift or serverless. We will show you serverless in another video. Anyway, let's keep deployment. We want a route that will expose our workload with a public URL, okay. And finally I want to set an environment variable that which is needed in my application. And I can easily do it from here. Look, I just typed the name of the key of my environment variable deployment and the value is a container image. In a few seconds you will understand why. When done, I hit create that will bring me back to the topology view. And here you can see that is my deployment here. So my deployment will create a pod. The pod is getting created. You can see that I have a service as well, a route. You can check the logs while it's getting created, you know. Oh look, it's done. You can see by the way it's a Quarkus app. Awesome. I will go back here to my topology and I should have my application running. Let me control that. Yeah, there we are. My application is running. I can hit the route that was created for me and that brings me here and I do slash hello on my end point and it's a hello developer sandbox for that open shift. This has been deployed with a container image, a container image exactly. That is the value of my environment variable. That's why I needed to set it. Okay. So that was the first option. You see pretty easy. I just point to my container image and it's get deployed. Let's go to the other option I go back here to add. And this time, well, I'm developer and I know how to work with Git. I know how to do my Git commit, my Git push, how to handle pull requests, etc. And the great thing here with the sandbox is that you can point directly to a Git repo. Okay. And OpenShift will take care of cloning your repo, building the project, depending if it's a Java project and Node.js, he knows a lot of technologies, he will handle that for you. Okay. And then he will create an image, push it in the internal registry of OpenShift and again, create a deployment and create a pod, etc., the route. Let's see that together. Click here. And again, here, even simpler, the only thing that they can enter here is a Git URL. Okay. So here you can just hit right to the URL of your repo. In my case, it's on GitHub on my personal repo and it's called HelloSendBox, okay. By the way, you can just go there on my repo, fork it, play with it if you want. Look at this builder image detected. That means he detected that it is a Java project. So he has here, he will be using a Java OpenGTK builder image. That's just great. That has Maven and all the things I need. The name, let me change the name here. Let me call it HelloSendBoxGit, again, deployment, deployment config or serverless deployment. Let's keep deployment for now. I want the route to be created and just like before, I want to set my environment variable. Deployment this time, the value will be a Git repo. And I hit create. Again, I will go back to the topology view and I should see here my second workload, okay. And this time it will take a bit more time. I'm not in front of it now. Look at this. Waiting for the build. Because this time he needs to do a bit more stuff. He needs to clone a repo. That is pretty fast. But then he needs to build my project. And it's a Java Maven project. So he has to download all the dependencies. By the way, you can take a look at the build as so. You can take a look at the logs of the build. So here you can see that he did the clone, Git clone, okay. And here in a few seconds, he will start downloading for me all the dependencies. Look at this. You can see it here. All the Quarkus dependencies, what he's needed. So it takes some time, okay. That is the first time. Of course, there's always the possibility of installing like a local Nexus in your sandbox. Just running as a pod that will contain a cache of all your dependencies. If you want your builds to go faster, okay. Here I'm just using a fresh environment. So he needs to download everything. Anyway, it should just take a matter of seconds. It's a pretty small project, okay. And when it will be done, again, as I explained you, he will create a container image for this. He will push it in an internal registry of OpenShift. Then he will create the deployment resource, the service, the route, etc. And we will be all set, okay. So I'm checking here. Should be all good. We can go back to the topology. I'm just checking for when it will be good. Let me take a look here. So waiting for the build. Yeah, it's a bit longer. Build is still running. Anyway, let's cross fingers. Yeah, there we go. Build completed. There we go. So he's making my pod. My pod is running awesome. I can access my public route here. I go to slash, hello. And I should see, hello developer sandbox for Red Hat OpenShift. It has been deployed with a Git repo, okay. So we are sure these are two different applications. Well, it's the same application, but deployed in a different way. But bring us to the third option, okay. And it is, you might be a Java developer and you don't really know how to make a container. You haven't put your project yet on Git, but you want to try it out on the sandbox, okay. One thing that you know how to do is creating a jar because that's when you do a Maven clean install, it creates a jar. So you have a renewable jar. And you know what? There's one option here to just drag and drop your jar from your local computer to this sandbox. Let me show you. So I built project just before. I can show it to you here. Look at this. I just did the build just before here, build success, okay. That has created the jar for me. And here I have my file system with my jar, my renewable jar. And look at this. I can just grab this jar and bring it over. Look, just bring it over here. Drop jar file here. Just like when I upload a video on YouTube, drag and drop. There we go. Upload jar. I want the icon Java. That's okay for me. I want to call this hello sandbox jar, okay. A deployment, exactly all the same options that you saw before, okay. And deployment, I set here my environment variable. Using a jar file, okay. I hit create, that will bring me back to the topology. And here you can see that my jar file is uploading. Again, it needs to do a build. It will be faster this time because it doesn't need to build the Java project. It doesn't need to do the main build because it's already there. What it needs to do is to create the container image. Okay, so let's take some times. Let me take a look here, but it should be faster. You just need to create an image. And when the image will be made, it should be available here on my topology. Let's be patient and then we can check, okay. You might wonder here, for the second one here, what this icon is, edit source code. We will see that in another video, but since I grabbed my app from Git, I can also directly edit my source code. We will see that in another video. When I was speaking, look at this. My jar has been uploaded. I can click here. I can go to the end point. Hello, and look at this. Hello developer sandbox for Red Hat OpenShift. This has been deployed with a jar file. So conclusion. Here in around 11 minutes, I show you three different ways of deploying your application. I do a quick recap using a container image, using a Git repo and uploading your jar file. You can try it out right now. You know, you can access the developer sandbox. Let me go here. If you go to developers.redhat.com slash developer sandbox, okay. You can for free, okay. You just need a Red Hat developer account and no credit card as just a phone number. You can get your own instance for 30 days and you can renew it as long as you want. And you will have access to all of that I just show you and even more. But this stuff that I will show you in another video. Have fun with the sandbox. Bye bye.