diff --git a/mysql-wordpress-pd/README.md b/mysql-wordpress-pd/README.md
index 873191ba..9c1e6770 100644
--- a/mysql-wordpress-pd/README.md
+++ b/mysql-wordpress-pd/README.md
@@ -66,7 +66,7 @@ First, **edit [`mysql.yaml`](mysql.yaml)**, the mysql pod definition, to use a d
 `mysql.yaml` looks like this:
 
 ```yaml
-apiVersion: v1beta3
+apiVersion: v1
 kind: Pod
 metadata:
   name: mysql
@@ -135,7 +135,7 @@ So if we label our Kubernetes mysql service `mysql`, the wordpress pod will be a
 The [`mysql-service.yaml`](mysql-service.yaml) file looks like this:
 
 ```yaml
-apiVersion: v1beta3
+apiVersion: v1
 kind: Service
 metadata: 
   labels: 
@@ -170,7 +170,7 @@ Once the mysql service is up, start the wordpress pod, specified in
 Note that this config file also defines a volume, this one using the `wordpress-disk` persistent disk that you created.
 
 ```yaml
-apiVersion: v1beta3
+apiVersion: v1
 kind: Pod
 metadata:
   name: wordpress
@@ -220,23 +220,23 @@ Once the wordpress pod is running, start its service, specified by [`wordpress-s
 The service config file looks like this:
 
 ```yaml
-apiVersion: v1beta3
+apiVersion: v1
 kind: Service
 metadata: 
   labels: 
     name: wpfrontend
   name: wpfrontend
 spec: 
-  createExternalLoadBalancer: true
   ports:
     # the port that this service should serve on
     - port: 80
   # label keys and values that must match in order to receive traffic for this service
   selector: 
     name: wordpress
+  type: LoadBalancer
 ```
 
-Note the `createExternalLoadBalancer` setting.  This will set up the wordpress service behind an external IP.
+Note the `type: LoadBalancer` setting.  This will set up the wordpress service behind an external IP.
 Note also that we've set the service port to 80.  We'll return to that shortly.
 
 Start the service:
@@ -251,8 +251,12 @@ and see it in the list of services:
 $ kubectl get services
 ```
 
-Then, find the external IP for your WordPress service by listing the forwarding rules for your project:
+Then, find the external IP for your WordPress service by running:
+```
+$ kubectl get services/wpfrontend --template="{{range .status.loadBalancer.ingress}} {{.ip}} {{end}}"
+```
 
+or by listing the forwarding rules for your project:
 ```shell
 $ gcloud compute forwarding-rules list
 ```
diff --git a/mysql-wordpress-pd/mysql-service.yaml b/mysql-wordpress-pd/mysql-service.yaml
index c8e0c55a..e2bbd939 100644
--- a/mysql-wordpress-pd/mysql-service.yaml
+++ b/mysql-wordpress-pd/mysql-service.yaml
@@ -1,4 +1,4 @@
-apiVersion: v1beta3
+apiVersion: v1
 kind: Service
 metadata: 
   labels: 
diff --git a/mysql-wordpress-pd/mysql.yaml b/mysql-wordpress-pd/mysql.yaml
index b94c5607..4bb3d998 100644
--- a/mysql-wordpress-pd/mysql.yaml
+++ b/mysql-wordpress-pd/mysql.yaml
@@ -1,4 +1,4 @@
-apiVersion: v1beta3
+apiVersion: v1
 kind: Pod
 metadata:
   name: mysql
diff --git a/mysql-wordpress-pd/wordpress-service.yaml b/mysql-wordpress-pd/wordpress-service.yaml
index 3a8573d1..6157b770 100644
--- a/mysql-wordpress-pd/wordpress-service.yaml
+++ b/mysql-wordpress-pd/wordpress-service.yaml
@@ -1,14 +1,14 @@
-apiVersion: v1beta3
+apiVersion: v1
 kind: Service
 metadata: 
   labels: 
     name: wpfrontend
   name: wpfrontend
 spec: 
-  createExternalLoadBalancer: true
   ports:
     # the port that this service should serve on
     - port: 80
   # label keys and values that must match in order to receive traffic for this service
   selector: 
     name: wordpress
+  type: LoadBalancer
diff --git a/mysql-wordpress-pd/wordpress.yaml b/mysql-wordpress-pd/wordpress.yaml
index 56230ab3..33ae07f7 100644
--- a/mysql-wordpress-pd/wordpress.yaml
+++ b/mysql-wordpress-pd/wordpress.yaml
@@ -1,4 +1,4 @@
-apiVersion: v1beta3
+apiVersion: v1
 kind: Pod
 metadata:
   name: wordpress