Table of Contents

1. Challenge

   Create the GKE Cluster and Storage Class

   1. Create a three-node GKE standard cluster using the n1-standard-1 instance type.
   2. Create a new storage class object to utilize SSD persistent disks. You can use the ssd-storageclass.yaml file in the supporting Git repo.
2. Challenge

   Create Persistent Volumes

   1. Create persistent volume claims for MySQL and Wordpress. You can use the mysql-pvc.yaml and wordpress-pvc.yaml files in the supporting Git repo.
3. Challenge

   Deploy MySQL

   1. Create a secret object called mysql to store the MySQL DB root password. If you are using the mysql-secret.yaml file in the GitHub repo, you should change the value of the password for security reasons. You will need to base64 encode a new value.

   2. Create the MySQL deployment. You can use the mysql-deployment.yaml file in the GitHub repo.

   3. Create the MySQL service. You can use the mysql-service.yaml file in the GitHub repo.

      echo -n mypassword | base64 -w 0
      

4. Challenge

   Deploy WordPress

   1. Create the WordPress deployment. You can use the wordpress-deployment.yaml file in the GitHub repo.
   2. Create the WordPress service. You can use the wordpress-service.yaml file in the GitHub repo.

   It will take a few minutes for the GCP load balancer to assign a public IP address, after which you should be able to access the WordPress site by following the link from the Services & Ingress tab in the GKE section of the GCP console.

   You should then be able to access your new installation.

   Note: WordPress installations can be insecure, and you should not leave yours running for long before concluding and stopping this lab.