We've talked a lot about WordPress, now its time to deploy it. We've included the base files to deploy WordPress in
./resources. Your job is to modify these files to use ConfigMaps, Secrets, and Persistent Volumes and Claims.
The database backing WordPress is MySQL in this instance. In the included Deployment manifest, we specified a password for the database directly via an environment variable. However, that couples the configuration to the actual Deployment, which is something we'd like to avoid.
Kubernetes Secrets allow us to decouple this information from the actual application.
Your job is to create a password and store it as a Kubernetes Secret for the MySQL Deployment to consume, and then update the Deployment to actually use it. You can accomplish this by creating a secret on the command line.
Once you've created your Secret, verify that it exists:
kubectl get secrets
The output of the command should look something like:
NAME TYPE DATA AGE mysql-pass Opaque 1 42s