update examples/meteor to v1

meteor/README.md

@@ -96,12 +96,12 @@ kubectl create -f meteor-controller.json
 kubectl create -f meteor-service.json
 ```
 
-Note that [`meteor-service.json`](meteor-service.json) creates an external load balancer, so
+Note that [`meteor-service.json`](meteor-service.json) creates a load balancer, so
 your app should be available through the IP of that load balancer once
 the Meteor pods are started. You can find the IP of your load balancer
 by running:
 ```
-kubectl get services/meteor -o template -t "{{.spec.publicIPs}}"
+kubectl get services/meteor --template="{{range .status.loadBalancer.ingress}} {{.ip}} {{end}}"
 ```
 
 You will have to open up port 80 if it's not open yet in your

meteor/meteor-controller.json

@@ -1,6 +1,6 @@
 {
   "kind": "ReplicationController",
-  "apiVersion": "v1beta3",
+  "apiVersion": "v1",
   "metadata": {
     "name": "meteor-controller",
     "labels": {

meteor/meteor-service.json

@@ -1,13 +1,12 @@
 {
   "kind": "Service",
-  "apiVersion": "v1beta3",
+  "apiVersion": "v1",
   "metadata": {
     "name": "meteor"
   },
   "spec": {
     "ports": [
       {
-        "protocol": "TCP",
         "port": 80,
         "targetPort": "http-server"
       }
@@ -15,7 +14,7 @@
     "selector": {
       "name": "meteor"
     },
-    "createExternalLoadBalancer": true,
-    "sessionAffinity": "ClientIP"
+    "sessionAffinity": "ClientIP",
+    "type": "LoadBalancer"
   }
 }

meteor/mongo-pod.json

@@ -1,6 +1,6 @@
 {
   "kind": "Pod",
-  "apiVersion": "v1beta3",
+  "apiVersion": "v1",
   "metadata": {
     "name": "mongo",
     "labels": {

meteor/mongo-service.json

@@ -1,6 +1,6 @@
 {
   "kind": "Service",
-  "apiVersion": "v1beta3",
+  "apiVersion": "v1",
   "metadata": {
     "name": "mongo",
     "labels": {