From e3674c5554c454182ac86eba2663acb9218b0941 Mon Sep 17 00:00:00 2001 From: Rhys Powell Date: Thu, 31 May 2018 02:25:55 +0100 Subject: [PATCH] Update mysql-wordpress-persistent-volume.md (#8822) Update type: Loadbalancer to match whats in the manifest --- .../stateful-application/mysql-wordpress-persistent-volume.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md b/content/en/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md index a47c589055..1f6bd8fbc1 100644 --- a/content/en/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md +++ b/content/en/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md @@ -127,7 +127,7 @@ The following manifest describes a single-instance MySQL Deployment. The MySQL c ## Deploy WordPress -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. +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: LoadBalancer`. This setting exposes WordPress to traffic from outside of the cluster. {{< code file="mysql-wordpress-persistent-volume/wordpress-deployment.yaml" >}}