jmhbnz/workshops
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updates for exercise2.

Browse Source
This commit is contained in:
James Blair
2024-07-25 12:35:16 +12:00
parent 5d6d8a5412
commit 147f547bda
1 changed files with 14 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
data/workshop/exercise2.mdx
View File

@ -8,14 +8,12 @@ authors: ['default']
summary: "Time to deploy your first app!" summary: "Time to deploy your first app!"
--- ---
Now that we have had a tour of the OpenShift web console to get familiar, let's use the web console to deploy our first application. Now that we have had a tour of the OpenShift web console to get familiar, let's use the web console to deploy our first application.
Let’s start by doing the simplest thing possible - get a plain old Docker-formatted container image to run on OpenShift. This is incredibly simple to do. With OpenShift it can be done directly from the web console. Let’s start by doing the simplest thing possible - get a plain old [OCI](https://opencontainers.org) format container image to run on OpenShift. This is incredibly simple to do. With OpenShift it can be done directly from the web console.
Before we begin, if you would like a bit more background on what a container is or why they are important click the following link to learn more: https://www.redhat.com/en/topics/containers#overview Before we begin, if you would like a bit more background on what a container is or why they are important click the following link to learn more: https://www.redhat.com/en/topics/containers#overview
## 2.1 - Deploying the container image ## 2.1 - Deploying the container image
In this exercise, we’re going to deploy the **web** component of the ParksMap application which uses OpenShift's service discovery mechanism to discover any accompanying backend services deployed and shows their data on the map. Below is a visual overview of the complete ParksMap application. In this exercise, we’re going to deploy the **web** component of the ParksMap application which uses OpenShift's service discovery mechanism to discover any accompanying backend services deployed and shows their data on the map. Below is a visual overview of the complete ParksMap application.
@ -40,7 +38,7 @@ Leave all other fields at their defaults (but take your time to scroll down and
Click **Create** to deploy the application. Click **Create** to deploy the application.
OpenShift will pull this container image if it does not exist already on the cluster and then deploy a container based on this image. You will be taken back to the **Topology** view in the **Developer** perspective which will show the new "Parksmap" application. OpenShift will create a [`Deployment`](https://docs.openshift.com/container-platform/4.16/applications/deployments/what-deployments-are.html) that will pull this container image if it does not exist already on the cluster and create a [`Pod`](https://docs.openshift.com/container-platform/4.16/nodes/pods/nodes-pods-using.html) that our container will run inside. You will be taken back to the **Topology** view in the **Developer** perspective which will show the new "Parksmap" application.
<Zoom> <Zoom>
|![first-app](/static/images/first-app.gif) | |![first-app](/static/images/first-app.gif) |
@ -48,12 +46,11 @@ OpenShift will pull this container image if it does not exist already on the clu
| *Deploying the container image* | | *Deploying the container image* |
</Zoom> </Zoom>
## 2.2 - Reviewing our deployed application ## 2.2 - Reviewing our deployed application
If you click on the **parksmap** entry in the **Topology** view, you will see some information about that deployed application. If you click on the **parksmap** entry in the **Topology** view, you will see some information about that deployed application.
The **Resources** tab may be displayed by default. If so, click on the **Details** tab. On that tab, you will see that there is a single **Pod** that was created by your actions. The **Resources** tab may be displayed by default. If so, click on the **Details** tab. On that tab, you will see that there is a single `Pod` that was created by your actions.
<Zoom> <Zoom>
|![app-details](/static/images/app-details.gif) | |![app-details](/static/images/app-details.gif) |
@ -63,12 +60,11 @@ The **Resources** tab may be displayed by default. If so, click on the **Details
> Note: A pod is the smallest deployable unit in Kubernetes and is effectively a grouping of one or more individual containers. Any containers deployed within a pod are guaranteed to run on the same machine. It is very common for pods in kubernetes to only hold a single container, although sometimes auxiliary services can be included as additional containers in a pod when we want them to run alongside our application container. > Note: A pod is the smallest deployable unit in Kubernetes and is effectively a grouping of one or more individual containers. Any containers deployed within a pod are guaranteed to run on the same machine. It is very common for pods in kubernetes to only hold a single container, although sometimes auxiliary services can be included as additional containers in a pod when we want them to run alongside our application container.
## 2.2 - Accessing the application ## 2.2 - Accessing the application
Now that we have the ParksMap application deployed. How do we access it?? Now that we have the ParksMap application deployed. How do we access it??
This is where OpenShift **Routes** and **Services** come in. This is where OpenShift [`Routes`](https://docs.openshift.com/container-platform/4.16/networking/routes/route-configuration.html) and [`Services`](https://docs.openshift.com/container-platform/4.16/rest_api/network_apis/service-v1.html) come in.
While **Services** provide internal abstraction and load balancing within an OpenShift cluster, sometimes clients outside of the OpenShift cluster need to access an application. The way that external clients are able to access applications running in OpenShift is through an OpenShift **Route**. While **Services** provide internal abstraction and load balancing within an OpenShift cluster, sometimes clients outside of the OpenShift cluster need to access an application. The way that external clients are able to access applications running in OpenShift is through an OpenShift **Route**.
@ -90,7 +86,6 @@ Clicking the link you should now see the ParksMap application frontend 🎉
| *ParksMap application frontend* | | *ParksMap application frontend* |
</Zoom> </Zoom>
## 2.3 - Checking application logs ## 2.3 - Checking application logs
If we deploy an application and something isn't working the way we expect, reviewing the application logs can often be helpful. OpenShift includes built in support for reviewing application logs. If we deploy an application and something isn't working the way we expect, reviewing the application logs can often be helpful. OpenShift includes built in support for reviewing application logs.
@ -109,16 +104,13 @@ From the **Resources** tab click **View logs**
| *Accessing the ParksMap application logs* | | *Accessing the ParksMap application logs* |
</Zoom> </Zoom>
## 2.4 - Checking application resource usage ## 2.4 - Checking application resource usage
Another essential element of supporting applications on OpenShift is understanding what resources the application is consuming, for example cpu, memory, network bandwidth and storage io. Another essential element of supporting applications on OpenShift is understanding what resources the application is consuming, for example cpu, memory, network bandwidth and storage io.
OpenShift includes built in support for reviewing application resource usage. Let's take a look at that now. OpenShift includes built in support for reviewing application resource usage. Let's take a look at that now.
In the **Developer** perspective, open the **Observe** view. In the **Developer** perspective, open the **Observe** view. You should see the **Dashboard** tab.
You should see the **Dashboard** tab. Set the time range to the `Last 1 hour` then scroll through the dashboard.
How much cpu and memory is your ParksMap application currently using? How much cpu and memory is your ParksMap application currently using?