kubernetes/cluster/vagrant
Eric Tune 9044177bb6 Generate a token for kube-proxy.
Tested on GCE.
Includes untested modifications for AWS and Vagrant.
No changes for any other distros.
Probably will work on other up-to-date providers
but beware.  Symptom would be that service proxying
stops working.

 1. Generates a token kube-proxy in AWS, GCE, and Vagrant setup scripts.
 1. Distributes the token via salt-overlay, and salt to /var/lib/kube-proxy/kubeconfig
 1. Changes kube-proxy args:
   - use the --kubeconfig argument
   - changes --master argument from http://MASTER:7080 to https://MASTER
     - http -> https
     - explicit port 7080 -> implied 443

Possible ways this might break other distros:

Mitigation: there is an default empty kubeconfig file.
If the distro does not populate the salt-overlay, then
it should get the empty, which parses to an empty
object, which, combined with the --master argument,
should still work.

Mitigation:
  - azure: Special case to use 7080 in
  - rackspace: way out of date, so don't care.
  - vsphere: way out of date, so don't care.
  - other distros: not using salt.
2015-04-27 08:59:57 -07:00
..
config-default.sh Fix vagrant regression from 6691 2015-04-21 00:44:44 -04:00
config-test.sh Standardize how we refer to the kubernetes root. 2014-10-10 12:33:36 -07:00
pod-ip-test.sh Rework vagrant cluster set up. 2014-12-17 13:23:39 -08:00
provision-master.sh Generate a token for kube-proxy. 2015-04-27 08:59:57 -07:00
provision-minion.sh Rename salt minion_ip to hostname_override 2015-04-21 06:24:49 -07:00
provision-network.sh Fix vagrant with etcd in pod 2015-04-02 16:55:29 -04:00
util.sh kube-controller-manager in a pod. 2015-04-20 16:06:37 -07:00