Red Hat OpenShift Sandboxed Containers | Red Hat OpenShift, 17 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Red Hat OpenShift sandboxed containers 101 - Jenkins deployment

Description

Running Jenkins or similar workloads inside sandboxed containers on the Red Hat OpenShift is quite easy. All it takes is adding a runtime class name to your workload manifest file.

Learn more: https://www.redhat.com/en/openshift-sandboxed-containers

A

Hello in a previous video, we saw how to deploy the openshift sandbox containers operator, I'm going to assume that this is done and that when you click on the list of install operators, you do see the openshift sandbox containers operator over here and that when you click on it, you have a catacon fig.

A

In my case it was called democala config, where you have, the installation is not in progress, so is in progress is false and the runtime class is kera.

A

If that's what you see, you're all set to deploy a part that uses sandbox containers.

A

So for this example, I'm going to create a demo project, so I give it the name gmo and add a short description.

A

Let me now create a pod, so first I'm going to create a standard example pod, I'm not going to use kerala containers or sandbox containers and when I hit create- and I look at the logs I'm going to see that my command line, the httpd process has started and if I know now look at the terminal for this pod, I'm going to see the processes that run inside so four instances of httpd.

A

But I can also check the uptime, which is the time of my cluster 25 minutes here, and I can look, for instance, at the command line for the kernel and that's the typical common line. You expect when you're running directly on your node.

A

So this is what happens with the normal known cata non sandboxed containers.

A

Let me now do the same thing, but now I'm going to do the same thing with sandbox containers. All I need to do is to add a runtime class name here with the value cata and that's going to now start my sandbox my container in a sandbox. So I need a new name.

A

And you can see that the container is creating. That takes slightly more time, because now it's starting a new virtual machine to run my container.

A

The container is now running and if I look at the logs, I'm going to see exactly the same thing that I saw before with http being started, and if I connect to a terminal, it looks very similar. The same processes are running inside.

A

However, if I look at the uptime, what I see now is that it's just been just been up. It's the uptime of the virtual machine, and we can check that by comparing the command line and checking that the command line looks different. It has only two cpus, for instance, and we are actually running inside the virtual machine.

A

Let us now do something slightly more complicated where we are going to do a complete deployment, so I have a prepared deployment there for 10 kids. The name is jenkins. That's the image. I used the values options and you see that I added ports and volumes, so this is slightly more complicated than before and I'm simply going to apply that manifest in the demo project.

A

And once this is deployed, I can watch the pause to check that this has been running and you see the amount of time it's been running.

A

Now, to make this available outside of the cluster, I can also deploy service and I'm now going to check that my ports are running that my deployments on my deployment. In that case single one, is running and that the service itself is now available.

A

Let me return to my console and I can now look at my deployments.

A

Inside the demo project, there is this single jenkins deployment.

A

And if I now look at the services, there is the single jenkins service which, as you can see, is exposed here on port 30 000..

A

I can now connect to my jenkins application and check that it actually runs, for instance, by clicking on new item and checking that the application responds.

A

Let me now return to my console and do the same kind of deployments, except now, I'm going to try with the cada runtime class name.

A

So if I make a difference between the two yaml files, the one that has a kera in the name and the one without you're going to see that the only difference is the name of the deployment itself and the fact that I added runtime class name in the jenkins scala deployments file.

A

So let me actually delete the all deployments and that's because I want to even reuse the service.

A

And now I can instead apply the cada deployment, their version of the deployment.

A

We can now check in the console that the service is still running, that the deployment is now my jenkins scala deployment and that one is running inside sandbox containers.

A

And if I now go to my application- and I refresh you, see that it's restarting and it's getting ready to work.

A

Now it's available and I can again create a new item and check that the application is responding.