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

Compare commits

base: jmhbnz:666aa64a1b5e3a3fdaa26da6c3dabdba351e3d7a
Branches Tags
jmhbnz:main
..
compare: jmhbnz:372524a6debba388f0038cdf6c3db59d7f1a8155
Branches Tags
jmhbnz:main

2 Commits
666aa64a1b ... 372524a6de

Author SHA1 Message Date
James Blair
372524a6de Start working on openshift disconnected lab. 2023-12-18 20:18:19 +13:00
James Blair
e17f1f2367 Begin making the repository a monorepo for workshops. 2023-12-18 19:45:42 +13:00
26 changed files with 2666 additions and 12579 deletions
Expand all files Collapse all files

4
LICENSE
View File

@ -208,7 +208,7 @@ If you develop a new program, and you want it to be of the greatest possible use
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
ocp-app-delivery-workshop workshops
Copyright (C) 2023 jmhbnz Copyright (C) 2023 jmhbnz
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
@ -221,7 +221,7 @@ Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
ocp-app-delivery-workshop Copyright (C) 2023 jmhbnz workshops Copyright (C) 2023 jmhbnz
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.

5
README.org
View File

@ -1,11 +1,10 @@
#+TITLE: OpenShift Application Delivery Workshop #+TITLE: OpenShift Workshops
#+AUTHOR: James Blair #+AUTHOR: James Blair
#+DATE: <2023-12-04 Mon> #+DATE: <2023-12-04 Mon>
This repository contains a basic [[https://nextjs.org/][nextjs]] frontend designed to be exported as a static site and served via [[https://pages.github.com/][github pages]]. This repository contains a basic [[https://nextjs.org/][nextjs]] frontend designed to be exported as a static site and served via [[https://pages.github.com/][github pages]].
The frontend contains a walkthrough for workshop designed to be run over three hours covering basic application delivery, monitoring and security on OpenShift. The workshop content is tailored towards participants that are new to containers and kubernetes and will not be developing applications but will instead be expected to deliver existing applications onto OpenShift. The frontend is used to serve workshop instructions for several workshops.
** Local development ** Local development

191
data/app-delivery/exercise1.mdx Normal file
View File

@ -0,0 +1,191 @@
---
title: Getting familiar with OpenShift
exercise: 1
date: '2023-12-04'
tags: ['openshift','containers','kubernetes']
draft: false
authors: ['default']
summary: "In this first exercise we'll get familiar with OpenShift."
---
Red Hat [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift) is a unified platform to build, modernize, and deploy applications at scale. In this first excercise we'll get logged into our cluster and familarise ourselves with the OpenShift web console and web terminal.
The OpenShift Container Platform web console is a feature-rich user interface with both an **Administrator** perspective and a **Developer** perspective accessible through any modern web browser. You can use the web console to visualize, browse, and manage your OpenShift cluster and the applications running on it.
In addition to the web console, OpenShift includes command line tools to provide users with a nice interface to work with applications deployed to the platform. The `oc` command line tool is available for Linux, macOS or Windows.
**Let's get started!**
## 1.1 - Login to lab environment
An OpenShift `4.14` cluster has already been provisioned for you to complete these excercises. Open your web browser and navigate to the workshop login page https://demo.redhat.com/workshop/enwmgc.
Once the page loads you can login with the details provided by your workshop facilitator.
<Zoom>
|![workshop](/workshops/static/images/workshop.png) |
|:-----------------------------------------------------------------------------:|
| *Workshop login page* |
</Zoom>
## 1.2 - Login to the cluster web console
Once you're logged into the lab environnment we can open up the OpenShift web console and login with the credentials provided.
When first logging in you will be prompted to take a tour of the **Developer** console view, let's do that now.
<Zoom>
| ![tour](/workshops/static/images/tour.gif) |
|:-----------------------------------------------------------------------------:|
| *Developer perspective web console tour* |
</Zoom>
## 1.3 - Understanding projects
Projects are a logical boundary to help you organize your applications. An OpenShift project allows a community of users (or a single user) to organize and manage their work in isolation from other projects.
Each project has its own resources, role based access control (who can or cannot perform actions), and constraints (quotas and limits on resources, etc).
Projects act as a "wrapper" around all the application services you (or your teams) are using for your work.
In this lab environment, you already have access to single project: `userX` (Where X is the number of your user allocted for the workshop from the previous step.)
Let's click into our `Project` from the left hand panel of the **Developer** web console perspective. We should be able to see that our project has no `Deployments` and there are no compute cpu or memory resources currently being consumed.
<Zoom>
|![project](/workshops/static/images/project.png) |
|:-----------------------------------------------------------------------------:|
| *Developer perspective project view* |
</Zoom>
## 1.4 - Switching between perspectives
Different roles have different needs when it comes to viewing details within the OpenShift web console. At the top of the left navigation menu, you can toggle between the Administrator perspective and the Developer perspective.
Select **Administrator** to switch to the Administrator perspective.
Once the Administrator perspective loads, you should be in the "Home" view and see a wider array of menu sections in the left hand navigation panel.
Switch back to the **Developer** perspective. Once the Developer perspective loads, select the **Topology** view.
Right now, there are no applications or components to view in your `userX` project, but once you begin working on the lab, you’ll be able to visualize and interact with the components in your application here.
<Zoom>
|![perspectives](/workshops/static/images/perspectives.gif) |
|:-----------------------------------------------------------------------------:|
| *Switching web console perspectives* |
</Zoom>
## 1.5 - Launching a web terminal
While web interfaces are comfortable and easy to use, sometimes we want to quickly run commands to get things done. That is where the `oc` command line utility comes in.
One handy feature of the OpenShift web console is we can launch a web terminal that will create a browser based terminal that already has the `oc` command logged in and ready to use.
Let's launch a web terminal now by clicking the terminal button in the top right hand corner and then clicking **Start** with our `userX` project selected.
<Zoom>
|![web-terminal](/workshops/static/images/web-terminal.gif) |
|:-----------------------------------------------------------------------------:|
| *Launching your web terminal* |
</Zoom>
## 1.6 - Running oc commands
The [`oc` command line utility](https://docs.openshift.com/container-platform/4.14/cli_reference/openshift_cli/getting-started-cli.html#creating-a-new-app) is a superset of the upstream kubernetes `kubectl` command line utility. This means it can do everything that `kubectl` can do, plus some additional OpenShift specific commands.
Let's try a few commands now:
### Checking our current project
Most actions we take in OpenShift will be in relation to a particular project. We can check which project we are currently actively using by running the `oc project` command.
We should see output similar to below showing we are currently using our `userX` project:
```bash
bash-4.4 ~ $ oc project
Using project "user1" from context named "user1-context" on server "https://172.31.0.1:443".
```
### Getting help and explaining concepts
As with any command line utility, there can be complexity that quickly surfaces. Thankfully the `oc` command line utility has excellent built in help.
Let's take a look at that now.
To get an understanding of all the options available, try running `oc help`. You should see options similar to the below sample:
```text
bash-4.4 ~ $ oc help
OpenShift Client
This client helps you develop, build, deploy, and run your applications on any
OpenShift or Kubernetes cluster. It also includes the administrative
commands for managing a cluster under the 'adm' subcommand.
Basic Commands:
login Log in to a server
new-project Request a new project
new-app Create a new application
status Show an overview of the current project
project Switch to another project
projects Display existing projects
explain Get documentation for a resource
Build and Deploy Commands:
rollout Manage a Kubernetes deployment or OpenShift deployment config
rollback Revert part of an application back to a previous deployment
new-build Create a new build configuration
start-build Start a new build
cancel-build Cancel running, pending, or new builds
import-image Import images from a container image registry
tag Tag existing images into image streams
```
To get a more detailed explanataion about a specific concept we can use the `oc explain` command.
Let's run `oc explain project` now to learn more about the concept of a project we introduced earlier:
```text
bash-4.4 ~ $ oc explain project
KIND: Project
VERSION: project.openshift.io/v1
DESCRIPTION:
Projects are the unit of isolation and collaboration in OpenShift. A
project has one or more members, a quota on the resources that the project
may consume, and the security controls on the resources in the project.
Within a project, members may have different roles - project administrators
can set membership, editors can create and manage the resources, and
viewers can see but not access running containers. In a normal cluster
project administrators are not able to alter their quotas - that is
restricted to cluster administrators.
Listing or watching projects will return only projects the user has the
reader role on.
An OpenShift project is an alternative representation of a Kubernetes
namespace. Projects are exposed as editable to end users while namespaces
are not. Direct creation of a project is typically restricted to
administrators, while end users should use the requestproject resource.
```
That's a quick introduction to the `oc` command line utility. Let's close our web terminal now so we can move on to the next excercise.
<Zoom>
|![close-terminal](/workshops/static/images/close-terminal.gif) |
|:-----------------------------------------------------------------------------:|
| *Closing your web terminal* |
</Zoom>
Well done, you've finished exercise 1! 🎉

14
data/workshop/exercise2.mdx → data/app-delivery/exercise2.mdx
View File

@ -21,7 +21,7 @@ Before we begin, if you would like a bit more background on what a container is
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.
<Zoom> <Zoom>
|![parksmap-architecture](/ocp-app-delivery-workshop/static/images/parksmap-architecture.png) | |![parksmap-architecture](/workshops/static/images/parksmap-architecture.png) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *ParksMap application architecture* | | *ParksMap application architecture* |
</Zoom> </Zoom>
@ -43,7 +43,7 @@ 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 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.
<Zoom> <Zoom>
|![first-app](/ocp-app-delivery-workshop/static/images/first-app.gif) | |![first-app](/workshops/static/images/first-app.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Deploying the container image* | | *Deploying the container image* |
</Zoom> </Zoom>
@ -56,7 +56,7 @@ If you click on the **parksmap** entry in the **Topology** view, you will see so
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](/ocp-app-delivery-workshop/static/images/app-details.gif) | |![app-details](/workshops/static/images/app-details.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Deploying the container image* | | *Deploying the container image* |
</Zoom> </Zoom>
@ -75,7 +75,7 @@ While **Services** provide internal abstraction and load balancing within an Ope
You may remember that when we deployed the ParksMap application, there was a checkbox ticked to automatically create a **Route**. Thanks to this, all we need to do to access the application is go the **Resources** tab of the application details pane and click the url shown under the **Routes** header. You may remember that when we deployed the ParksMap application, there was a checkbox ticked to automatically create a **Route**. Thanks to this, all we need to do to access the application is go the **Resources** tab of the application details pane and click the url shown under the **Routes** header.
<Zoom> <Zoom>
|![app-details](/ocp-app-delivery-workshop/static/images/app-route.gif) | |![app-details](/workshops/static/images/app-route.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Opening ParksMap application Route* | | *Opening ParksMap application Route* |
</Zoom> </Zoom>
@ -85,7 +85,7 @@ Clicking the link you should now see the ParksMap application frontend 🎉
> Note: If this is the first time opening this page, the browser will ask permission to get your position. This is needed by the Frontend app to center the world map to your location, if you don’t allow it, it will just use a default location. > Note: If this is the first time opening this page, the browser will ask permission to get your position. This is needed by the Frontend app to center the world map to your location, if you don’t allow it, it will just use a default location.
<Zoom> <Zoom>
|![app-frontend](/ocp-app-delivery-workshop/static/images/app-frontend.png) | |![app-frontend](/workshops/static/images/app-frontend.png) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *ParksMap application frontend* | | *ParksMap application frontend* |
</Zoom> </Zoom>
@ -104,7 +104,7 @@ Click your "Parksmap" application icon then click on the **Resources** tab.
From the **Resources** tab click **View logs** From the **Resources** tab click **View logs**
<Zoom> <Zoom>
|![app-logs](/ocp-app-delivery-workshop/static/images/app-logs.gif) | |![app-logs](/workshops/static/images/app-logs.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Accessing the ParksMap application logs* | | *Accessing the ParksMap application logs* |
</Zoom> </Zoom>
@ -123,7 +123,7 @@ You should see the **Dashboard** tab. Set the time range to the `Last 1 hour` th
How much cpu and memory is your ParksMap application currently using? How much cpu and memory is your ParksMap application currently using?
<Zoom> <Zoom>
|![app-logs](/ocp-app-delivery-workshop/static/images/app-resources.gif) | |![app-logs](/workshops/static/images/app-resources.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Checking the ParksMap application resource usage* | | *Checking the ParksMap application resource usage* |
</Zoom> </Zoom>

6
data/workshop/exercise3.mdx → data/app-delivery/exercise3.mdx
View File

@ -31,7 +31,7 @@ spec:
``` ```
<Zoom> <Zoom>
|![parksmap-replicas](/ocp-app-delivery-workshop/static/images/app-replicas.gif) | |![parksmap-replicas](/workshops/static/images/app-replicas.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *ParksMap application deployment replicas* | | *ParksMap application deployment replicas* |
</Zoom> </Zoom>
@ -58,7 +58,7 @@ kill 1
The pod will automatically be restarted by OpenShift however if you refresh your second browser tab with the application **Route** you should be able to see the application is momentarily unavailable. The pod will automatically be restarted by OpenShift however if you refresh your second browser tab with the application **Route** you should be able to see the application is momentarily unavailable.
<Zoom> <Zoom>
|![parksmap-crash](/ocp-app-delivery-workshop/static/images/app-crash.gif) | |![parksmap-crash](/workshops/static/images/app-crash.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Intentionally crashing the ParksMap application* | | *Intentionally crashing the ParksMap application* |
</Zoom> </Zoom>
@ -79,7 +79,7 @@ In the **Details** tab of the information pane click the **^ Increase the pod co
Once the new pod is ready, repeat the steps from task `3.2` to crash one of the pods. You should see that the application continues to serve traffic thanks to our OpenShift **Service** load balancing traffic to the second **Pod**. Once the new pod is ready, repeat the steps from task `3.2` to crash one of the pods. You should see that the application continues to serve traffic thanks to our OpenShift **Service** load balancing traffic to the second **Pod**.
<Zoom> <Zoom>
|![parksmap-scale](/ocp-app-delivery-workshop/static/images/app-scale.gif) | |![parksmap-scale](/workshops/static/images/app-scale.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Scaling up the ParksMap application* | | *Scaling up the ParksMap application* |
</Zoom> </Zoom>

10
data/workshop/exercise4.mdx → data/app-delivery/exercise4.mdx
View File

@ -39,7 +39,7 @@ tlsRoute: true
``` ```
<Zoom> <Zoom>
|![gitea-deployment](/ocp-app-delivery-workshop/static/images/gitea-deployment.gif) | |![gitea-deployment](/workshops/static/images/gitea-deployment.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Gitea application deployment via helm chart* | | *Gitea application deployment via helm chart* |
</Zoom> </Zoom>
@ -63,7 +63,7 @@ Next, if we click on the overall gitea **Helm release** by clicking on the shade
> Note: Feel free to try out a `oc explain <resource>` command in your web terminal to learn more about each of the resource types mentioned above, for example `oc explain service`. > Note: Feel free to try out a `oc explain <resource>` command in your web terminal to learn more about each of the resource types mentioned above, for example `oc explain service`.
<Zoom> <Zoom>
|![helm-resources](/ocp-app-delivery-workshop/static/images/helm-resources.png) | |![helm-resources](/workshops/static/images/helm-resources.png) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Gitea helm release resources created* | | *Gitea helm release resources created* |
</Zoom> </Zoom>
@ -86,7 +86,7 @@ We will be returned to the **Helm releases** view. Notice how the release status
From here it is trivial to perform a **Rollback** to remove our misconfigured update. We'll do that in the next step. From here it is trivial to perform a **Rollback** to remove our misconfigured update. We'll do that in the next step.
<Zoom> <Zoom>
|![helm-upgrade](/ocp-app-delivery-workshop/static/images/helm-upgrade.gif) | |![helm-upgrade](/workshops/static/images/helm-upgrade.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Attempting a gitea helm upgrade* | | *Attempting a gitea helm upgrade* |
</Zoom> </Zoom>
@ -105,7 +105,7 @@ Click the three dot menu to the right hand side of the that helm release and cli
Select the radio button for revision `1` which should be showing a status of `Deployed`, then click **Rollback**. Select the radio button for revision `1` which should be showing a status of `Deployed`, then click **Rollback**.
<Zoom> <Zoom>
|![helm-rollback](/ocp-app-delivery-workshop/static/images/helm-rollback.gif) | |![helm-rollback](/workshops/static/images/helm-rollback.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Rolling back to a previous gitea helm release* | | *Rolling back to a previous gitea helm release* |
</Zoom> </Zoom>
@ -126,7 +126,7 @@ Click the three dot menu to the right hand side of the that helm release and cli
Enter the `gitea` confirmation at the prompt and click **Delete**. If you now return to the **Topology** view you will see the gitea application deleting. Enter the `gitea` confirmation at the prompt and click **Delete**. If you now return to the **Topology** view you will see the gitea application deleting.
<Zoom> <Zoom>
|![helm-delete](/ocp-app-delivery-workshop/static/images/helm-delete.gif) | |![helm-delete](/workshops/static/images/helm-delete.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Deleting the gitea application helm release* | | *Deleting the gitea application helm release* |
</Zoom> </Zoom>

8
data/workshop/exercise5.mdx → data/app-delivery/exercise5.mdx
View File

@ -52,7 +52,7 @@ Paste the above snippet of YAML into the editor and replace the instance of `use
Click **Create**. In a minute or so you should see the Grafana operator installed and running in your project. Click **Create**. In a minute or so you should see the Grafana operator installed and running in your project.
<Zoom> <Zoom>
|![operator-deployment](/ocp-app-delivery-workshop/static/images/operator-deployment.gif) | |![operator-deployment](/workshops/static/images/operator-deployment.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Deploying grafana operator via static yaml* | | *Deploying grafana operator via static yaml* |
</Zoom> </Zoom>
@ -100,7 +100,7 @@ spec:
``` ```
<Zoom> <Zoom>
|![grafana-deployment](/ocp-app-delivery-workshop/static/images/grafana-deployment.gif) | |![grafana-deployment](/workshops/static/images/grafana-deployment.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Deploying grafana application via the grafana operator* | | *Deploying grafana application via the grafana operator* |
</Zoom> </Zoom>
@ -115,7 +115,7 @@ For our first step click on the **Workloads** category on the left hand side men
We should see that a `grafana-deployment-<id>` pod with a **Status** of `Running`. We should see that a `grafana-deployment-<id>` pod with a **Status** of `Running`.
<Zoom> <Zoom>
|![grafana-pod](/ocp-app-delivery-workshop/static/images/grafana-pod.png) | |![grafana-pod](/workshops/static/images/grafana-pod.png) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Confirming the grafana pod is running* | | *Confirming the grafana pod is running* |
</Zoom> </Zoom>
@ -130,7 +130,7 @@ Click the **Route** named `grafana-route` and open the url on the right hand sid
Once the new tab opens we should be able to login to Grafana using the credentials we supplied in the previous step in the YAML configuration. Once the new tab opens we should be able to login to Grafana using the credentials we supplied in the previous step in the YAML configuration.
<Zoom> <Zoom>
|![grafana-route](/ocp-app-delivery-workshop/static/images/grafana-route.gif) | |![grafana-route](/workshops/static/images/grafana-route.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Confirming the grafana route is working* | | *Confirming the grafana route is working* |
</Zoom> </Zoom>

2
data/workshop/exercise6.mdx → data/app-delivery/exercise6.mdx
View File

@ -46,7 +46,7 @@ Scroll down and under the **General** header click the **Application** drop down
Scroll down reviewing the other options then click **Create**. Scroll down reviewing the other options then click **Create**.
<Zoom> <Zoom>
|![s2i-build](/ocp-app-delivery-workshop/static/images/s2i-build.gif) | |![s2i-build](/workshops/static/images/s2i-build.gif) |
|:-------------------------------------------------------------------:| |:-------------------------------------------------------------------:|
| *Creating a source to image build in OpenShift* | | *Creating a source to image build in OpenShift* |
</Zoom> </Zoom>

10
data/authors/default.md
View File

@ -1,8 +1,8 @@
name: Red Hat name: James Blair
avatar: /static/images/redhat.png avatar: /static/images/redhat.png
occupation: TSSC Workshop occupation: Specialist Architect
company: Open Source company: Red Hat
email: redhat@redhat.com email: jablair@redhat.com
twitter: https://twitter.com/RedHat twitter: https://twitter.com/RedHat
github: https://github.com/RedHat github: https://github.com/jmhbnz
linkedin: https://www.linkedin.com/in/RedHat linkedin: https://www.linkedin.com/in/RedHat

12
data/authors/sparrowhawk.md
View File

@ -1,12 +0,0 @@
---
name: Sparrow Hawk
avatar: /static/images/sparrowhawk-avatar.jpg
occupation: Wizard of Earthsea
company: Earthsea
twitter: https://twitter.com/sparrowhawk
linkedin: https://www.linkedin.com/sparrowhawk
---
At birth Ged was given the child-name Duny by his mother. He was born on the island of Gont, son of a bronzesmith. His mother died before he reached the age of one. As a small boy, Ged had overheard the village witch, his maternal aunt, using various words of power to call goats. Ged later used the words without understanding of their meanings, to surprising effect.
The witch knew that using words of power effectively without understanding them required innate power, so she endeavored to teach him what little she knew. After learning more from her, he was able to call animals to him. Particularly, he was seen in the company of wild sparrowhawks so often that his "use name" became Sparrowhawk.

8
data/siteMetadata.js
View File

@ -1,11 +1,11 @@
const siteMetadata = { const siteMetadata = {
title: 'Red Hat OpenShift Application Delivery Workshop', title: 'Red Hat OpenShift Workshops',
author: 'Red Hat', author: 'Red Hat',
headerTitle: 'Red Hat', headerTitle: 'Red Hat',
description: 'Red Hat OpenShift Application Delivery Workshop', description: 'Red Hat OpenShift Workshops',
language: 'en-us', language: 'en-us',
siteUrl: 'https://jmhbnz.github.io/ocp-app-delivery-workshop', siteUrl: 'https://jmhbnz.github.io/workshops',
siteRepo: 'https://github.com/jmhbnz/ocp-app-delivery-workshop', siteRepo: 'https://github.com/jmhbnz/workshops',
siteLogo: '/static/images/redhat.png', siteLogo: '/static/images/redhat.png',
image: '/static/images/avatar.png', image: '/static/images/avatar.png',
socialBanner: '/static/images/twitter-card.png', socialBanner: '/static/images/twitter-card.png',

168
data/workshop/exercise1.mdx
View File

@ -1,11 +1,11 @@
--- ---
title: Getting familiar with OpenShift title: Understanding the lab environment
exercise: 1 exercise: 1
date: '2023-12-04' date: '2023-12-18'
tags: ['openshift','containers','kubernetes'] tags: ['openshift','containers','kubernetes']
draft: false draft: false
authors: ['default'] authors: ['default']
summary: "In this first exercise we'll get familiar with OpenShift." summary: "Let's get familiar with the lab setup."
--- ---
Red Hat [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift) is a unified platform to build, modernize, and deploy applications at scale. In this first excercise we'll get logged into our cluster and familarise ourselves with the OpenShift web console and web terminal. Red Hat [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift) is a unified platform to build, modernize, and deploy applications at scale. In this first excercise we'll get logged into our cluster and familarise ourselves with the OpenShift web console and web terminal.
@ -23,169 +23,9 @@ An OpenShift `4.14` cluster has already been provisioned for you to complete the
Once the page loads you can login with the details provided by your workshop facilitator. Once the page loads you can login with the details provided by your workshop facilitator.
<Zoom> <Zoom>
|![workshop](/ocp-app-delivery-workshop/static/images/workshop.png) | |![workshop](/workshops/static/images/workshop.png) |
|:-----------------------------------------------------------------------------:| |:-----------------------------------------------------------------------------:|
| *Workshop login page* | | *Workshop login page* |
</Zoom> </Zoom>
## 1.2 - Login to the cluster web console
Once you're logged into the lab environnment we can open up the OpenShift web console and login with the credentials provided.
When first logging in you will be prompted to take a tour of the **Developer** console view, let's do that now.
<Zoom>
| ![tour](/ocp-app-delivery-workshop/static/images/tour.gif) |
|:-----------------------------------------------------------------------------:|
| *Developer perspective web console tour* |
</Zoom>
## 1.3 - Understanding projects
Projects are a logical boundary to help you organize your applications. An OpenShift project allows a community of users (or a single user) to organize and manage their work in isolation from other projects.
Each project has its own resources, role based access control (who can or cannot perform actions), and constraints (quotas and limits on resources, etc).
Projects act as a "wrapper" around all the application services you (or your teams) are using for your work.
In this lab environment, you already have access to single project: `userX` (Where X is the number of your user allocted for the workshop from the previous step.)
Let's click into our `Project` from the left hand panel of the **Developer** web console perspective. We should be able to see that our project has no `Deployments` and there are no compute cpu or memory resources currently being consumed.
<Zoom>
|![project](/ocp-app-delivery-workshop/static/images/project.png) |
|:-----------------------------------------------------------------------------:|
| *Developer perspective project view* |
</Zoom>
## 1.4 - Switching between perspectives
Different roles have different needs when it comes to viewing details within the OpenShift web console. At the top of the left navigation menu, you can toggle between the Administrator perspective and the Developer perspective.
Select **Administrator** to switch to the Administrator perspective.
Once the Administrator perspective loads, you should be in the "Home" view and see a wider array of menu sections in the left hand navigation panel.
Switch back to the **Developer** perspective. Once the Developer perspective loads, select the **Topology** view.
Right now, there are no applications or components to view in your `userX` project, but once you begin working on the lab, you’ll be able to visualize and interact with the components in your application here.
<Zoom>
|![perspectives](/ocp-app-delivery-workshop/static/images/perspectives.gif) |
|:-----------------------------------------------------------------------------:|
| *Switching web console perspectives* |
</Zoom>
## 1.5 - Launching a web terminal
While web interfaces are comfortable and easy to use, sometimes we want to quickly run commands to get things done. That is where the `oc` command line utility comes in.
One handy feature of the OpenShift web console is we can launch a web terminal that will create a browser based terminal that already has the `oc` command logged in and ready to use.
Let's launch a web terminal now by clicking the terminal button in the top right hand corner and then clicking **Start** with our `userX` project selected.
<Zoom>
|![web-terminal](/ocp-app-delivery-workshop/static/images/web-terminal.gif) |
|:-----------------------------------------------------------------------------:|
| *Launching your web terminal* |
</Zoom>
## 1.6 - Running oc commands
The [`oc` command line utility](https://docs.openshift.com/container-platform/4.14/cli_reference/openshift_cli/getting-started-cli.html#creating-a-new-app) is a superset of the upstream kubernetes `kubectl` command line utility. This means it can do everything that `kubectl` can do, plus some additional OpenShift specific commands.
Let's try a few commands now:
### Checking our current project
Most actions we take in OpenShift will be in relation to a particular project. We can check which project we are currently actively using by running the `oc project` command.
We should see output similar to below showing we are currently using our `userX` project:
```bash
bash-4.4 ~ $ oc project
Using project "user1" from context named "user1-context" on server "https://172.31.0.1:443".
```
### Getting help and explaining concepts
As with any command line utility, there can be complexity that quickly surfaces. Thankfully the `oc` command line utility has excellent built in help.
Let's take a look at that now.
To get an understanding of all the options available, try running `oc help`. You should see options similar to the below sample:
```text
bash-4.4 ~ $ oc help
OpenShift Client
This client helps you develop, build, deploy, and run your applications on any
OpenShift or Kubernetes cluster. It also includes the administrative
commands for managing a cluster under the 'adm' subcommand.
Basic Commands:
login Log in to a server
new-project Request a new project
new-app Create a new application
status Show an overview of the current project
project Switch to another project
projects Display existing projects
explain Get documentation for a resource
Build and Deploy Commands:
rollout Manage a Kubernetes deployment or OpenShift deployment config
rollback Revert part of an application back to a previous deployment
new-build Create a new build configuration
start-build Start a new build
cancel-build Cancel running, pending, or new builds
import-image Import images from a container image registry
tag Tag existing images into image streams
```
To get a more detailed explanataion about a specific concept we can use the `oc explain` command.
Let's run `oc explain project` now to learn more about the concept of a project we introduced earlier:
```text
bash-4.4 ~ $ oc explain project
KIND: Project
VERSION: project.openshift.io/v1
DESCRIPTION:
Projects are the unit of isolation and collaboration in OpenShift. A
project has one or more members, a quota on the resources that the project
may consume, and the security controls on the resources in the project.
Within a project, members may have different roles - project administrators
can set membership, editors can create and manage the resources, and
viewers can see but not access running containers. In a normal cluster
project administrators are not able to alter their quotas - that is
restricted to cluster administrators.
Listing or watching projects will return only projects the user has the
reader role on.
An OpenShift project is an alternative representation of a Kubernetes
namespace. Projects are exposed as editable to end users while namespaces
are not. Direct creation of a project is typically restricted to
administrators, while end users should use the requestproject resource.
```
That's a quick introduction to the `oc` command line utility. Let's close our web terminal now so we can move on to the next excercise.
<Zoom>
|![close-terminal](/ocp-app-delivery-workshop/static/images/close-terminal.gif) |
|:-----------------------------------------------------------------------------:|
| *Closing your web terminal* |
</Zoom>
Well done, you've finished exercise 1! 🎉

4
next.config.js
View File

@ -11,8 +11,8 @@ module.exports = withBundleAnalyzer({
images: { images: {
unoptimized: true unoptimized: true
}, },
basePath: '/ocp-app-delivery-workshop', basePath: '/workshops',
assetPrefix: '/ocp-app-delivery-workshop/', assetPrefix: '/workshops/',
experimental: { esmExternals: true }, experimental: { esmExternals: true },
webpack: (config, { dev, isServer }) => { webpack: (config, { dev, isServer }) => {
config.module.rules.push({ config.module.rules.push({

14357
package-lock.json generated
View File

File diff suppressed because it is too large Load Diff

2
package.json
View File

@ -1,5 +1,5 @@
{ {
"name": "ocp-app-delivery-workshop", "name": "workshops",
"version": "0.0.1", "version": "0.0.1",
"private": true, "private": true,
"scripts": { "scripts": {

32
public/feed.xml
View File

@ -1,19 +1,19 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel> <channel>
<title>Red Hat OpenShift Application Delivery Workshop</title> <title>Red Hat OpenShift Workshops</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link> <link>https://jmhbnz.github.io/workshops/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description> <description>Red Hat OpenShift Workshops</description>
<language>en-us</language> <language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor> <managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster> <webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Mon, 04 Dec 2023 00:00:00 GMT</lastBuildDate> <lastBuildDate>Mon, 04 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/feed.xml" rel="self" type="application/rss+xml"/> <atom:link href="https://jmhbnz.github.io/workshops/feed.xml" rel="self" type="application/rss+xml"/>
<item> <item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise1</guid> <guid>https://jmhbnz.github.io/workshops/workshop/exercise1</guid>
<title>Getting familiar with OpenShift</title> <title>Getting familiar with OpenShift</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise1</link> <link>https://jmhbnz.github.io/workshops/workshop/exercise1</link>
<description>In this first exercise we&#39;ll get familiar with OpenShift.</description> <description>In this first exercise we&#39;ll get familiar with OpenShift.</description>
<pubDate>Mon, 04 Dec 2023 00:00:00 GMT</pubDate> <pubDate>Mon, 04 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author> <author>jablair@redhat.com (Red Hat)</author>
@ -21,9 +21,9 @@
</item> </item>
<item> <item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</guid> <guid>https://jmhbnz.github.io/workshops/workshop/exercise2</guid>
<title>Deploying your first application</title> <title>Deploying your first application</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</link> <link>https://jmhbnz.github.io/workshops/workshop/exercise2</link>
<description>Time to deploy your first app!</description> <description>Time to deploy your first app!</description>
<pubDate>Tue, 05 Dec 2023 00:00:00 GMT</pubDate> <pubDate>Tue, 05 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author> <author>jablair@redhat.com (Red Hat)</author>
@ -31,9 +31,9 @@
</item> </item>
<item> <item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</guid> <guid>https://jmhbnz.github.io/workshops/workshop/exercise3</guid>
<title>Scaling and self-healing applications</title> <title>Scaling and self-healing applications</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</link> <link>https://jmhbnz.github.io/workshops/workshop/exercise3</link>
<description>Let&#39;s scale our application up 📈</description> <description>Let&#39;s scale our application up 📈</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate> <pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author> <author>jablair@redhat.com (Red Hat)</author>
@ -41,9 +41,9 @@
</item> </item>
<item> <item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</guid> <guid>https://jmhbnz.github.io/workshops/workshop/exercise4</guid>
<title>Deploying an application via helm chart</title> <title>Deploying an application via helm chart</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</link> <link>https://jmhbnz.github.io/workshops/workshop/exercise4</link>
<description>Exploring alternative deployment approaches.</description> <description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate> <pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author> <author>jablair@redhat.com (Red Hat)</author>
@ -51,9 +51,9 @@
</item> </item>
<item> <item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</guid> <guid>https://jmhbnz.github.io/workshops/workshop/exercise5</guid>
<title>Deploying an application via operator</title> <title>Deploying an application via operator</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</link> <link>https://jmhbnz.github.io/workshops/workshop/exercise5</link>
<description>Exploring alternative deployment approaches.</description> <description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate> <pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author> <author>jablair@redhat.com (Red Hat)</author>
@ -61,9 +61,9 @@
</item> </item>
<item> <item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</guid> <guid>https://jmhbnz.github.io/workshops/workshop/exercise6</guid>
<title>Deploying an application from source</title> <title>Deploying an application from source</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</link> <link>https://jmhbnz.github.io/workshops/workshop/exercise6</link>
<description>Exploring alternative deployment approaches.</description> <description>Exploring alternative deployment approaches.</description>
<pubDate>Thu, 07 Dec 2023 00:00:00 GMT</pubDate> <pubDate>Thu, 07 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author> <author>jablair@redhat.com (Red Hat)</author>

24
public/tags/autoscaling/feed.xml
View File

@ -1,24 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Wed, 06 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/autoscaling/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</guid>
<title>Scaling and self-healing applications</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</link>
<description>Let&#39;s scale our application up 📈</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>autoscaling</category>
</item>
</channel>
</rss>

74
public/tags/containers/feed.xml
View File

@ -1,74 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Mon, 04 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/containers/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise1</guid>
<title>Getting familiar with OpenShift</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise1</link>
<description>In this first exercise we&#39;ll get familiar with OpenShift.</description>
<pubDate>Mon, 04 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</guid>
<title>Deploying your first application</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</link>
<description>Time to deploy your first app!</description>
<pubDate>Tue, 05 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>images</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</guid>
<title>Scaling and self-healing applications</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</link>
<description>Let&#39;s scale our application up 📈</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>autoscaling</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</guid>
<title>Deploying an application via helm chart</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>helm</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</guid>
<title>Deploying an application via operator</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>operator-framework</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</guid>
<title>Deploying an application from source</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Thu, 07 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>s2i</category><category>shipwright</category>
</item>
</channel>
</rss>

44
public/tags/deployments/feed.xml
View File

@ -1,44 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Tue, 05 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/deployments/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</guid>
<title>Deploying your first application</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</link>
<description>Time to deploy your first app!</description>
<pubDate>Tue, 05 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>images</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</guid>
<title>Scaling and self-healing applications</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</link>
<description>Let&#39;s scale our application up 📈</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>autoscaling</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</guid>
<title>Deploying an application via helm chart</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>helm</category>
</item>
</channel>
</rss>

24
public/tags/helm/feed.xml
View File

@ -1,24 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Wed, 06 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/helm/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</guid>
<title>Deploying an application via helm chart</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>helm</category>
</item>
</channel>
</rss>

24
public/tags/images/feed.xml
View File

@ -1,24 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Tue, 05 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/images/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</guid>
<title>Deploying your first application</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</link>
<description>Time to deploy your first app!</description>
<pubDate>Tue, 05 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>images</category>
</item>
</channel>
</rss>

74
public/tags/kubernetes/feed.xml
View File

@ -1,74 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Mon, 04 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/kubernetes/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise1</guid>
<title>Getting familiar with OpenShift</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise1</link>
<description>In this first exercise we&#39;ll get familiar with OpenShift.</description>
<pubDate>Mon, 04 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</guid>
<title>Deploying your first application</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</link>
<description>Time to deploy your first app!</description>
<pubDate>Tue, 05 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>images</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</guid>
<title>Scaling and self-healing applications</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</link>
<description>Let&#39;s scale our application up 📈</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>autoscaling</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</guid>
<title>Deploying an application via helm chart</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>helm</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</guid>
<title>Deploying an application via operator</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>operator-framework</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</guid>
<title>Deploying an application from source</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Thu, 07 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>s2i</category><category>shipwright</category>
</item>
</channel>
</rss>

74
public/tags/openshift/feed.xml
View File

@ -1,74 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Mon, 04 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/openshift/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise1</guid>
<title>Getting familiar with OpenShift</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise1</link>
<description>In this first exercise we&#39;ll get familiar with OpenShift.</description>
<pubDate>Mon, 04 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</guid>
<title>Deploying your first application</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise2</link>
<description>Time to deploy your first app!</description>
<pubDate>Tue, 05 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>images</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</guid>
<title>Scaling and self-healing applications</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise3</link>
<description>Let&#39;s scale our application up 📈</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>autoscaling</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</guid>
<title>Deploying an application via helm chart</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise4</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>deployments</category><category>helm</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</guid>
<title>Deploying an application via operator</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>operator-framework</category>
</item>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</guid>
<title>Deploying an application from source</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Thu, 07 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>s2i</category><category>shipwright</category>
</item>
</channel>
</rss>

24
public/tags/operator-framework/feed.xml
View File

@ -1,24 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Wed, 06 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/operator-framework/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</guid>
<title>Deploying an application via operator</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise5</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Wed, 06 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>operator-framework</category>
</item>
</channel>
</rss>

24
public/tags/s2-i/feed.xml
View File

@ -1,24 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Thu, 07 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/s2-i/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</guid>
<title>Deploying an application from source</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Thu, 07 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>s2i</category><category>shipwright</category>
</item>
</channel>
</rss>

24
public/tags/shipwright/feed.xml
View File

@ -1,24 +0,0 @@
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Red Hat OpenShift Application Delivery Workshop</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop</link>
<description>Red Hat OpenShift Application Delivery Workshop</description>
<language>en-us</language>
<managingEditor>jablair@redhat.com (Red Hat)</managingEditor>
<webMaster>jablair@redhat.com (Red Hat)</webMaster>
<lastBuildDate>Thu, 07 Dec 2023 00:00:00 GMT</lastBuildDate>
<atom:link href="https://jmhbnz.github.io/ocp-app-delivery-workshop/tags/shipwright/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<guid>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</guid>
<title>Deploying an application from source</title>
<link>https://jmhbnz.github.io/ocp-app-delivery-workshop/workshop/exercise6</link>
<description>Exploring alternative deployment approaches.</description>
<pubDate>Thu, 07 Dec 2023 00:00:00 GMT</pubDate>
<author>jablair@redhat.com (Red Hat)</author>
<category>openshift</category><category>containers</category><category>kubernetes</category><category>s2i</category><category>shipwright</category>
</item>
</channel>
</rss>