Add glide.yaml and vendor deps

vendor/k8s.io/kubernetes/cluster/saltbase/reactor/README.md

@@ -0,0 +1,6 @@
+[SaltStack reactor](http://docs.saltstack.com/en/latest/topics/reactor/) files, largely defining reactions to new nodes.
+
+**Ignored for GCE, which runs standalone on each machine**
+
+
+[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/cluster/saltbase/reactor/README.md?pixel)]()

vendor/k8s.io/kubernetes/cluster/saltbase/reactor/highstate-masters.sls

@@ -0,0 +1,10 @@
+# This runs highstate on the master node(s).
+#
+# Some of the cluster deployment scripts pass the list of minion addresses to
+# the apiserver as a command line argument. This list needs to be updated if a
+# new minion is started, so run highstate on the master(s) when this happens.
+#
+highstate_master:
+  cmd.state.highstate:
+    - tgt: 'roles:kubernetes-master'
+    - expr_form: grain

vendor/k8s.io/kubernetes/cluster/saltbase/reactor/highstate-minions.sls

@@ -0,0 +1,11 @@
+# This runs highstate on the minion nodes.
+#
+# Some of the cluster deployment scripts use the list of minions on the minions
+# themselves (for example: every minion is configured with static routes to
+# every other minion on a vSphere deployment). To propagate changes throughout
+# the pool, run highstate on all minions whenever a single minion starts.
+#
+highstate_minions:
+  cmd.state.highstate:
+    - tgt: 'roles:kubernetes-pool'
+    - expr_form: grain

vendor/k8s.io/kubernetes/cluster/saltbase/reactor/highstate-new.sls

@@ -0,0 +1,4 @@
+# This runs highstate only on the NEW node, regardless of type.
+highstate_new:
+  cmd.state.highstate:
+    - tgt: {{ data['id'] }}