From 3c8a775588f4b3ddb2e2309e7a7f4af647510fe4 Mon Sep 17 00:00:00 2001 From: Max Kuchin Date: Sun, 3 Sep 2017 09:58:08 +1000 Subject: [PATCH] Include filename fix (#5139) * Include filename fix mysql-deployment.yaml was included instead of wordpress-deployment.yaml in the last step. * removing footer change #5139 --- .../stateful-application/mysql-wordpress-persistent-volume.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md b/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md index 07a059dbac..217c0c9bfd 100644 --- a/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md +++ b/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md @@ -121,7 +121,7 @@ The following manifest describes a single-instance MySQL Deployment. The MySQL c The following manifest describes a single-instance WordPress Deployment and Service. It uses many of the same features like a PVC for persistent storage and a Secret for the password. But it also uses a different setting: `type: NodePort`. This setting exposes WordPress to traffic from outside of the cluster. -{% include code.html language="yaml" file="mysql-wordpress-persistent-volume/mysql-deployment.yaml" ghlink="/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/wordpress-deployment.yaml" %} +{% include code.html language="yaml" file="mysql-wordpress-persistent-volume/wordpress-deployment.yaml" ghlink="/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/wordpress-deployment.yaml" %} 1. Create a WordPress Service and Deployment from the `wordpress-deployment.yaml` file: