remove creationTimestamp fields from manifest examples

docs/bastion.md

@@ -34,7 +34,6 @@ You should now be able to edit and configure your bastion instance group.
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: "2017-01-05T13:37:07Z"
   name: bastions
 spec:
   associatePublicIp: true

docs/examples/kops-test-route53-subdomain.md

@@ -685,11 +685,10 @@ kops edit ig nodes
 
 An editor (whatever you have on the $EDITOR shell variable) will open with the following text:
 
-```
+```yaml
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-09-06T13:40:39Z
   labels:
     kops.k8s.io/cluster: mycluster01.kopsclustertest.example.org
   name: nodes
@@ -707,11 +706,10 @@ spec:
 
 Let's change minSize and maxSize to "3"
 
-```
+```yaml
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-09-06T13:40:39Z
   labels:
     kops.k8s.io/cluster: mycluster01.kopsclustertest.example.org
   name: nodes

docs/examples/kops-tests-private-net-bastion-host.md

@@ -142,11 +142,10 @@ kops create instancegroup bastions --role Bastion --subnet utility-us-east-1a --
 
 You'll see the following output in your editor when you can change your bastion group size and add more networks.
 
-```bash
+```yaml
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: null
   name: bastions
 spec:
   image: kope.io/k8s-1.7-debian-jessie-amd64-hvm-ebs-2017-07-28
@@ -320,11 +319,10 @@ kops edit ig bastions --name ${NAME}
 
 And change minSize/maxSize to 3 (3 instances) and add more subnets:
 
-```bash
+```yaml
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-08-28T17:05:23Z
   labels:
     kops.k8s.io/cluster: privatekopscluster.k8s.local
   name: bastions

docs/getting_started/gce.md

@@ -59,52 +59,53 @@ objects on a kubernetes cluster.
 
 You can see the details of your Cluster object by doing:
 
-    > kops get cluster --state ${KOPS_STATE_STORE}/ simple.k8s.local -oyaml
+`kops get cluster --state ${KOPS_STATE_STORE}/ simple.k8s.local -oyaml`
 
-    apiVersion: kops.k8s.io/v1alpha2
+```yaml
-    kind: Cluster
+apiVersion: kops.k8s.io/v1alpha2
-    metadata:
+kind: Cluster
-      creationTimestamp: 2017-10-03T05:07:27Z
+metadata:
-      name: simple.k8s.local
+  name: simple.k8s.local
-    spec:
+spec:
-      api:
+  api:
-        loadBalancer:
+    loadBalancer:
-          type: Public
+      type: Public
-      authorization:
+  authorization:
-        alwaysAllow: {}
+    alwaysAllow: {}
-      channel: stable
+  channel: stable
-      cloudProvider: gce
+  cloudProvider: gce
-      configBase: gs://kubernetes-clusters/simple.k8s.local
+  configBase: gs://kubernetes-clusters/simple.k8s.local
-      etcdClusters:
+  etcdClusters:
-      - etcdMembers:
+  - etcdMembers:
-        - instanceGroup: master-us-central1-a
+    - instanceGroup: master-us-central1-a
-          name: a
+      name: a
-        name: main
+    name: main
-      - etcdMembers:
+  - etcdMembers:
-        - instanceGroup: master-us-central1-a
+    - instanceGroup: master-us-central1-a
-          name: a
+      name: a
-        name: events
+    name: events
-      iam:
+  iam:
-        legacy: false
+    legacy: false
-      kubernetesApiAccess:
+  kubernetesApiAccess:
-      - 0.0.0.0/0
+  - 0.0.0.0/0
-      kubernetesVersion: 1.7.2
+  kubernetesVersion: 1.7.2
-      masterPublicName: api.simple.k8s.local
+  masterPublicName: api.simple.k8s.local
-      networking:
+  networking:
-        kubenet: {}
+    kubenet: {}
-      nonMasqueradeCIDR: 100.64.0.0/10
+  nonMasqueradeCIDR: 100.64.0.0/10
-      project: my-gce-project
+  project: my-gce-project
-      sshAccess:
+  sshAccess:
-      - 0.0.0.0/0
+  - 0.0.0.0/0
-      subnets:
+  subnets:
-      - name: us-central1
+  - name: us-central1
-        region: us-central1
+    region: us-central1
-        type: Public
+    type: Public
-      topology:
+  topology:
-        dns:
+    dns:
-          type: Public
+      type: Public
-        masters: public
+    masters: public
-        nodes: public
+    nodes: public
+```
 
 Similarly, you can also see your InstanceGroups using:
 

docs/iam_roles.md

@@ -108,7 +108,6 @@ After you're finished editing, your cluster spec should look something like this
 
 ```yaml
 metadata:
-  creationTimestamp: "2016-06-27T14:23:34Z"
   name: ${CLUSTER_NAME}
 spec:
   cloudProvider: aws

docs/manifests_and_customizing_via_api.md

@@ -60,7 +60,6 @@ The following is the contents of the exported YAML file.
 apiVersion: kops.k8s.io/v1alpha2
 kind: Cluster
 metadata:
-  creationTimestamp: 2017-05-04T23:21:47Z
   name: k8s.example.com
 spec:
   api:
@@ -137,7 +136,6 @@ spec:
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-05-04T23:21:48Z
   labels:
     kops.k8s.io/cluster: k8s.example.com
   name: bastions
@@ -158,7 +156,6 @@ spec:
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-05-04T23:21:47Z
   labels:
     kops.k8s.io/cluster: k8s.example.com
   name: master-us-east-2d
@@ -177,7 +174,6 @@ spec:
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-05-04T23:21:47Z
   labels:
     kops.k8s.io/cluster: k8s.example.com
   name: master-us-east-2b
@@ -196,7 +192,6 @@ spec:
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-05-04T23:21:48Z
   labels:
     kops.k8s.io/cluster: k8s.example.com
   name: master-us-east-2c
@@ -215,7 +210,6 @@ spec:
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-05-04T23:21:48Z
   labels:
     kops.k8s.io/cluster: k8s.example.com
   name: nodes
@@ -239,7 +233,6 @@ With the above YAML file, a user can add configurations that are not available v
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-05-04T23:21:48Z
   labels:
     kops.k8s.io/cluster: k8s.example.com
   name: my-crazy-big-nodes
@@ -292,7 +285,6 @@ Please refer to the rolling-update [documentation](cli/kops_rolling-update_clust
 apiVersion: kops.k8s.io/v1alpha2
 kind: Cluster
 metadata:
-  creationTimestamp: 2017-05-04T23:21:47Z
   name: k8s.example.com
 spec:
   api:
@@ -325,7 +317,6 @@ This command prints the entire YAML configuration. But _do not_ use the full doc
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-05-04T23:21:48Z
   name: foo
 spec:
 ```

docs/run_in_existing_vpc.md

@@ -19,7 +19,6 @@ When launching into a shared VPC, the VPC & the Internet Gateway will be reused.
 
   ```yaml
   metadata:
-    creationTimestamp: "2016-06-27T14:23:34Z"
     name: ${CLUSTER_NAME}
   spec:
     cloudProvider: aws
@@ -73,7 +72,6 @@ AWS now allows you to add more CIDRs to a VPC, the param `additionalNetworkCIDRs
 
 ```yaml
 metadata:
-  creationTimestamp: "2016-06-27T14:23:34Z"
   name: ${CLUSTER_NAME}
 spec:
   cloudProvider: aws
@@ -122,7 +120,6 @@ spec:
 
   ```yaml
   metadata:
-    creationTimestamp: "2016-06-27T14:23:34Z"
     name: ${CLUSTER_NAME}
   spec:
     cloudProvider: aws

docs/security_groups.md

@@ -20,7 +20,6 @@ Example:
 apiVersion: kops.k8s.io/v1alpha2
 kind: Cluster
 metadata:
-  creationTimestamp: "2016-12-10T22:42:27Z"
   name: mycluster.example.com
 spec:
   api:
@@ -34,7 +33,6 @@ spec:
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: "2017-01-01T00:00:00Z"
   labels:
     kops.k8s.io/cluster: mycluster.example.com
   name: master-us-test-1a

docs/tutorial/upgrading-kubernetes.md

@@ -13,7 +13,7 @@ Upgrading kubernetes is similar to changing the image on an InstanceGroup, excep
 controlled at the cluster level.  So instead of `kops edit ig <name>`, we `kops edit cluster`, and change the
 `kubernetesVersion` field.  `kops edit cluster` will open your editor with the cluster, similar to:
 
-```
+```yaml
 # Please edit the object below. Lines beginning with a '#' will be ignored,
 # and an empty file will abort the edit. If an error occurs while saving this file will be
 # reopened with the relevant failures.
@@ -21,7 +21,6 @@ controlled at the cluster level.  So instead of `kops edit ig <name>`, we `kops
 apiVersion: kops.k8s.io/v1alpha2
 kind: Cluster
 metadata:
-  creationTimestamp: 2017-10-04T03:52:25Z
   name: simple.k8s.local
 spec:
   api:

docs/tutorial/working-with-instancegroups.md

@@ -80,11 +80,10 @@ Let's change the number of nodes to 3.  We'll edit the InstanceGroup configurati
 should be very familiar to you if you've used `kubectl edit`).  `kops edit ig nodes` will open
 the InstanceGroup in your editor, looking a bit like this:
 
-```YAML
+```yaml
 apiVersion: kops.k8s.io/v1alpha2
 kind: InstanceGroup
 metadata:
-  creationTimestamp: 2017-10-03T15:17:31Z
   labels:
     kops.k8s.io/cluster: simple.k8s.local
   name: nodes