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
..
default	Generate a token for kube-proxy.	2015-04-27 08:59:57 -07:00
init.sls	Generate a token for kube-proxy.	2015-04-27 08:59:57 -07:00
initd	Raise the file ulimit for kube-proxy for init.d systems	2015-03-19 19:36:13 -04:00
kube-proxy.service	Fix to address issue #5461 kube-proxy too many files open	2015-03-17 10:13:25 -05:00
kubeconfig	Generate a token for kube-proxy.	2015-04-27 08:59:57 -07:00