X-dark
/
k8s-training-app
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add basic wordpress+MySQL lab

This commit is contained in:
Cedric Girard 2020-01-06 19:21:24 +01:00
parent b0912b0bc2
commit 7ed4bb9b77
1 changed files with 39 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
02_wordpress/README.md Normal file
View File

@ -0,0 +1,39 @@
# Wordpress lab
## Spawn a standalone Wordpress instance
* Create a Namespace.
* Deploy the `wordpress:5` image, using a `deployment` of one replica and exposing the port `80`.
* Try to connect to it using port forwarding from the hosting node.
* Confirm the Wordpress setup screen is available and that you need a database to complete the setup.
## Create a service to expose Wordpress
* Expose the Wordpress server, with a service to facilite access to it.
## Create a MariaDB database
* Deploy the `mariadb:10` image, using a `deployment` of one replica, exposing an environment variable called `MYSQL_ROOT_PASSWORD` containing the password of your choice and exposing the port `3306`.
#FIXME: the default config seems to only listen on localhost
* Create a `service` to expose the MariaDB server.
* Resume the Wordpress setup to use the newly created database.
* Delete the mariadb container to have it recreated.
* Go back to Wordpress and note that all previous work is now lost.
## Put Wordpress database settings into environment variables
* Edit the wordpress deployment and add the following environment variables with appropriate values:
* WORDPRESS_DB_HOST
* WORDPRESS_DB_NAME
* WORDPRESS_DB_USER
* WORDPRESS_DB_PASSWORD
* Confirm the database settings are now automatically configured.
## Persist the MariaDB volume
* Create a `PersistentVolumeClaim` to store MariaDB data.
* Modify the mariadb deployment to mount the new PersistentVolume into `/var/lib/mysql`
* Repeat the Wordpress setup
* Delete the mariadb container and confirm the Wordpress configuration is restored from the database.