At this point we have some theoretical knowledge of the OpenShift Container Platform. Let's take a look at the Web Console. This is going to be the interface that we are going to be using a lot in this course. I felt that I would actually take a look at the Developer Sandbox. I have logged in to the Developer Sandbox, and provisioned my Sandbox Environment. I can login to my Developer Sandbox Environment. One thing that I want to immediately point your attention to, is that the Developer Console has two perspectives. If you click this perspective, it has the Administrator, and Developer Perspective. In the Administrative Perspective, this is, as the name suggests, more of an administrative perspective. For example, you can verify the installed operators. If you have the Administrator rights on your OpenShift Cluster, you can, for example, deploy new operators. You can also take a look at all of the workloads within your Cluster. You can verify your networking, etc. In this particular cluster, we do not have the administrator privileges, and so therefore, this Administrative Perspective is mostly informative. It informs us of number 1, what has been created for us, and what is the status of the cluster, what is deployed in the cluster, etc. Number 2, what we have created, and for example, how we can delete it. This is the Administrator Perspective. I would definitely encourage you to, browse through the Administrative Perspective. Then we have the Developer Perspective. In the Developer Perspective, right now, it seems it is quite empty. What I want to bring your attention to is this ''Add'' section. This ''Add'' button. We can click the ''Add' button, and we see that there's a number of possibilities, and there is this subsection called Developer Catalog. This Developer Catalog contains a number of possibilities for us. Red Hat OpenShift Container Platform, comes with a number of pre-packaged templates, and services that are ready to be deployed. We have a number of databases, ready to be deployed. We have a number of languages that are supported. We have a number of Middleware product that Red Hat supports out of the gate just by default. For example, I can take a look at, some templates. Let's see all items, and for example, I can select this ''HTTPD Template''. When I click the ''Instantiate Template'' it brings me to this form. This form is exactly what we talked about. This is where you would specify, for example, the Git Repository URL, the Git Reference, which is the branch name, or a tag name or something similar, directory or host name or something similar. I will change the name, and this is just a demo. You do not have to follow along with me because we will have our guided exercise. But this is just, a interactive demonstration of what the OpenShift Web Console looks like. When I'm ready with the application, and I'm quite happy with the way it looks, I can see what exactly, the Template will create. I can click the ''Create'' button, and this kicks off the build and deploy process. Right now, we see that the build is spending. Let's wait until the build is complete, and our application is ready and available. Several things have happened with the application. Number 1, I can actually click the application. We see that there are a number of tabs. There is one part which is running. We see that the part is in a certain name space. It has some labels, et cetera. From our previous video, we know that the pod is what we care about the most. The pod is the actual application that is going to serve the content that we want to see. But notice that there's also the resource tab. In the resource tab, there are also other resources that the template has spawned for us. We have some builds and we see that there was one build that has completed and we see a service and a route. From our previous video, we know that a route should lead to our application. This is the URL that makes our application accessible on the Internet. If I click on this application, it should actually lead me to my application and that's correct. Based on basically prepackaged template in the OpenShift Container Platform. We have built and deployed an HTTPD based static website. Each of these resources has certain actions. Not only can I click on this location, but I can also click on the route. This route has certain actions associated with it. For example, I can delete this route and that's perfectly fine. If I return to the topology view, suddenly this application is no longer accessible from the Internet. One more thing that I wanted to mention is that we have deployed the application into a certain project. In the indie developer sandbox, we cannot create more projects. We only have two projects. A project is basically the same as namespace in Kubernetes. It's essentially where we encapsulate all of our resources. If I create an application into one of my projects, which is my username, dash Dev. My application lives in that particular project. If I switch to a different project, which is, for example, my username dash stage, my application will not be there. This is something to keep in mind. This course uses the dash dev project. But because we are using just a single project, it means that we have to clean the resources after we are done with the application. At the end of every guided exercise, we will be deleting our application just so that the name will not clash with other applications. What I mean is if in one guided exercise we create an application called instructor HTTPD demo or HTTP demo and we do not delete it in another guided exercise, we cannot create application with the same name. Because otherwise it with clash and we want to prevent that. What I can do is I can click action and delete deployment config. That's perfectly fine. I also want to delete the dependent objects of this resource and that will delete the actual part as well. We can also take a look whether there are some config maps and secrets. There seemed to be three ConfigMaps. We can delete these three ConfigMaps. There is an HTTPD example that seems to be also one of the secrets that God created. There we go. In the future, I will give you a better way of cleaning the cluster by using the command-line interface. For now, we're just going to use the web UI. That was our introduction to the Red Hat OpenShift container platform and the web console. Let's go ahead and deploy our own application to OpenShift in our guided exercise.