DO180 - ch05s04

Bookmark this page

Guided Exercise: Provision Persistent Data Volumes

Deploy a MySQL database with persistent storage from a PVC and identify the PV and storage provisioner that backs the application.

Outcomes

You should be able to do the following tasks:

Deploy a MySQL database with persistent storage from a PVC.
Identify the PV that backs the application.
Identify the storage provisioner that created the PV.

As the student user on the workstation machine, use the lab command to prepare your system for this exercise.

This command ensures that all resources are available for this exercise.

[student@workstation ~]$ lab start storage-volumes

Instructions

Log in to the OpenShift cluster as the developer user with the developer password. Select the storage-volumes project.
1. Use a web browser to navigate to the OpenShift web console at https://console-openshift-console.apps.ocp4.example.com.
2. Log in by using Red Hat Identity Management with the developer username and the developer password.
3. Select the Administrator view to access the administrative menu.
4. On the Home → Projects page, select the storage-volumes project.
Identify the default storage class for the cluster.
1. Select the Storage → StorageClasses menu option.
  Figure 5.18: Storage classes
  The nfs-storage storage class has the Default label.
Use the registry.ocp4.example.com:8443/rhel8/mysql-80 container image to create a MySQL deployment named db-pod. Use the storage-volumes project. Add a service for the database.
1. Select the Workloads → Deployments menu option.
2. Verify that the storage-volumes project is active and select the Create Deployment button.
3. Use db-pod for the deployment name and change the image name to registry.ocp4.example.com:8443/rhel8/mysql-80.
4. Add the environment variables.
  Table 5.5. MYSQL Environment Variables
  Name Value
  MYSQL_USER user1
  MYSQL_PASSWORD mypa55w0rd
  MYSQL_DATABASE items
5. Select the Advanced options → Scaling link and set the replicas to one.
6. Click Create. Wait for the blue circle to indicate that a single pod is running.
7. Click Networking → Services → Create Service.
8. Add the service values.
  Table 5.6. Service Fields
  Field name Value
  Name db-pod
  selector app=db-pod
  Port 3306
  Target port 3306
  
  Figure 5.19: Add Service
9. Click the Create button.
Add a 1 Gi, RWO PVC named db-pod-pvc to the deployment. Set the /var/lib/mysql directory as the mount path.
1. Select the Workloads → Deployments menu item.
2. Click the three vertical dots in the row with the db-pod deployment, and select the Add storage menu option.
3. In the Add Storage form, click Create new claim.
4. Add the following field values to the form.
  Table 5.7. Add PVC Storage Fields
  Field name Value
  PersistentVolumeClaim name db-pod-pvc
  Access mode RWO
  Size 1 GiB
  Volume mode Filesystem
  Mount path /var/lib/mysql
5. Click Save.
6. Scroll down in the deployment details to the Volumes section.
7. Select the db-pod-pvc link to see the PVC details.
  Figure 5.20: PVC Link

Name	Value
MYSQL_USER	user1
MYSQL_PASSWORD	mypa55w0rd
MYSQL_DATABASE	items

Field name	Value
Name	db-pod
selector	app=db-pod
Port	3306
Target port	3306

Field name	Value
PersistentVolumeClaim name	db-pod-pvc
Access mode	RWO
Size	1 GiB
Volume mode	Filesystem
Mount path	/var/lib/mysql

Observe how the volume mount changed the deployment.

Select the Workloads → Deployments → dp-pod → YAML tab.

Observe the volumes and volumeMounts additions to the deployment.

apiVersion: apps/v1
kind: Deployment

...output omitted...

      volumes:
      - name: nfs-volume-storage
        persistentVolumeClaim:
          claimName: db-pod-pvc

...output omitted...

        volumeMounts:
        - mountPath: /var/lib/mysql
          name: nfs-volume-storage

...output omitted...

Use a configuration map resource to add initialization data to the database.

Observe the contents of the init-db.sql script that initializes the database.

[student@workstation ~]$ cat \
~/DO180/labs/storage-volumes/configmap/init-db.sql

 DROP TABLE IF EXISTS `Item`;
 CREATE TABLE `Item` (`id` BIGINT not null auto_increment primary key, `description` VARCHAR(100), `done` BIT);
 INSERT INTO `Item` (`id`,`description`,`done`) VALUES (1,'Pick up newspaper', 0);
 INSERT INTO `Item` (`id`,`description`,`done`) VALUES (2,'Buy groceries', 1);

[student@workstation ~]$ oc login -u developer -p developer \
  https://api.ocp4.example.com:6443
Login successful.
...output omitted...

Set the storage-volumes project as the active project.

[student@workstation ~]$ oc project storage-volumes
...output omitted...

Use the contents of the init-db.sql file to create a configuration map named init-db-cm.

[student@workstation ~]$ oc create configmap init-db-cm \
--from-file=/home/student/DO180/labs/storage-volumes/configmap/init-db.sql
configmap/init-db-cm created

Add the init-db-cm configuration map resource as a volume named init-db-volume to the deployment. Specify the volume type as configmap, and set the /var/db/config directory as the mount path.

[student@workstation ~]$ oc set volumes deployment/db-pod \
--add --name init-db-volume --type configmap --configmap-name init-db-cm \
--mount-path /var/db/config
deployment.apps/db-pod volume updated

Start a remote shell session inside the container.

[student@workstation ~]$ oc rsh deployment/db-pod
sh-4.4$

Use the mysql client to execute the database script in the /var/db/config/init-db volume.

sh-4.4$ mysql -uuser1 -pmypa55w0rd items </var/db/config/init-db.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
sh-4.4$

Execute a query to verify the database contents.

sh-4.4$ mysql -uuser1 -pmypa55w0rd items -e 'select * from Item;'
mysql: [Warning] Using a password on the command line interface can be insecure.
+----+-------------------+------------+
| id | description       | done       |
+----+-------------------+------------+
|  1 | Pick up newspaper | 0x00       |
|  2 | Buy groceries     | 0x01       |
+----+-------------------+------------+
sh-4.4$

Exit the shell session.
```
sh-4.4$ exit
```

Delete and then re-create the db-pod deployment.

Delete the db-pod deployment.

[student@workstation ~]$ oc delete deployment/db-pod
deployment.apps "db-pod" deleted

Verify that the PVC still exists without the deployment.

[student@workstation ~]$ oc get pvc
NAME         STATUS   VOLUME                                     CAPACITY   ...
db-pod-pvc   Bound    pvc-ab5b38c7-359a-4e99-b81c-f7d11ef91cc9   1Gi        ...

Re-create the db-pod deployment.

[student@workstation ~]$ oc create deployment db-pod --port 3306 \
  --image=registry.ocp4.example.com:8443/rhel8/mysql-80
deployment.apps/db-pod created

Add the environment variables.

[student@workstation ~]$ oc set env deployment/db-pod \
  MYSQL_USER=user1 \
  MYSQL_PASSWORD=mypa55w0rd \
  MYSQL_DATABASE=items
deployment.apps/db-pod updated

Use the oc set volume command to attach the existing PVC to the deployment.

[student@workstation ~]$ oc set volumes deployment/db-pod \
  --add --type pvc \
  --mount-path /var/lib/mysql \
  --name db-pod-vol \
  --claim-name db-pod-pvc
deployment.apps/db-pod volume updated

Create a query-db pod by using the oc run command and the registry.ocp4.example.com:8443/redhattraining/do180-dbinit container image. Use the pod to execute a query against the database service.

Create the query-db pod. Configure the pod to use the MySQL client to execute a query against the db-pod service.

[student@workstation ~]$ oc run query-db -it --rm \
  --image registry.ocp4.example.com:8443/redhattraining/do180-dbinit \
  --restart Never \
  -- /bin/bash -c "mysql -uuser1 -pmypa55w0rd --protocol tcp \
  -h db-pod -P3306 items -e 'select * from Item;'"
mysql: [Warning] Using a password on the command line interface can be insecure.
+----+-------------------+------------+
| id | description       | done       |
+----+-------------------+------------+
|  1 | Pick up newspaper | 0x00       |
|  2 | Buy groceries     | 0x01       |
+----+-------------------+------------+
pod "query-db" deleted

Delete the db-pod deployment and the db-pod-pvc PVC.

Delete the db-pod deployment.

[student@workstation ~]$ oc delete deployment/db-pod
deployment.apps "db-pod" deleted

Delete the db-pod-pvc PVC.

[student@workstation ~]$ oc delete pvc/db-pod-pvc
persistentvolumeclaim "db-pod-pvc" deleted

Finish

On the workstation machine, use the lab command to complete this exercise. This step is important to ensure that resources from previous exercises do not impact upcoming exercises.

[student@workstation ~]$ lab finish storage-volumes

Discuss Red Hat OpenShift Administration I: Operating a Production Cluster

Go to community

Version 4.12.2 versus 4.12 of DO180 course?

DRobitaille

21 lis 2023

I just noticed that there is now a version 4.12.2 of the DO180. Currently without any new updated videos. Do we have access to some sort of changelog to judge how different the new version is compared to 4.12. I'm currently in the process of reviewing the content of DO180/DO280 in preparation for my upcoming EX280 exam (based on "4.12"), so I'm wondering if it's worth studying the 4.12.2 version instead of 4.12.

470

Red Hat OpenShift Administration I: Containers & Kubernetes (DO180)

Haley_Ruccio

20 lip 2023

Deploy, manage, and troubleshoot containerized applications running as Kubernetes workloads in OpenShift clusters.Course DescriptionRed Hat OpenShift Administration I: Managing Containers and Kubernetes (DO180) prepares OpenShift cluster administrators to manage Kubernetes workloads and to collaborate with developers, DevOps engineers, system administrators, and SREs to ensure the availability of application workloads. This course focuses on managing typical end-user applications that are often accessible from a web or mobile UI and that represent most cloud-native and containerized workloads. Managing applications also includes deploying and updating their dependencies, such as databases, messaging, and authentication systems.The skills that you learn in this course apply to all versions of OpenShift, including Red Hat OpenShift on AWS (ROSA), Azure Red Hat OpenShift, and OpenShift Container Platform.This course is based on Red Hat OpenShift 4.12.Course Content SummaryManaging OpenShift clusters from the command-line interface and from the web console.Troubleshooting network connectivity between applications inside and outside an OpenShift cluster.Connecting Kubernetes workloads to storage for application data.Configuring Kubernetes workloads for high availability and reliability.Managing updates to container images, settings, and Kubernetes manifests of an application.Target AudienceSystem administrators and platform operators who are interested in managing OpenShift clusters and containerized applications.Site Reliability Engineers who are interested in maintaining and troubleshooting containerized applications on Kubernetes.System and software architects who are interested in learning and using the features and functions of an OpenShift cluster.Developers and Site Reliability Engineers that are new to container technology should enroll in Red Hat OpenShift Development I: Introduction to Containers with Podman (DO188).Recommended trainingTake our free assessment to gauge whether this offering is the best fit for your skills.Prerequisite: Containers, Kubernetes and Red Hat OpenShift Technical Overview or equivalent knowledge of Linux containers.Technology considerationsThis course requires internet access to access the cloud-based classroom environment that provides an OpenShift cluster and a remote administrator’s workstation.

Welcome to the Red Hat OpenShift Administration (DO180) group in the Red Hat Learning Community!

Deanna

18 lip 2023

We are excited to launch a space dedicated to the Red Hat Training course Red Hat OpenShift Administration I - Containers & Kubernetes! To gain the most value from this group - click the "Join Group" button in the upper right hand corner of the group home screen.We encourage group members to collaborate in this group to discuss topics, ask questions, share best practices and tips, provide course feedback, and share their accomplishments as it relates to DO180.Read more about Red Hat OpenShift Administration I here.

114

Revision: do180-4.14-b6cd706