Joe Beda 5a0159ea00 Get Vagrant to start using TLS client certs. ...

Also fix up cert generation. It was failing during the first salt highstate when trying to chown the certs as the apiserver user didn't exist yet.  Fix this by creating a 'kube-cert' group and chgrping the files to that.  Then make the apiserver a member of that group.

Fixes #2365
Fixes #2368

2014-11-13 22:16:45 -08:00

..

aws

Give the API server access to TLS certs.

2014-11-12 18:14:24 -08:00

gce

Fix monitoring setup script.

2014-11-13 16:43:05 -05:00

local

Fix local cluster scripts

2014-11-02 23:30:14 -05:00

ovirt

Add support for oVirt cloud provider

2014-09-11 13:08:46 +00:00

rackspace

Fix monitoring setup script.

2014-11-13 16:43:05 -05:00

saltbase

Get Vagrant to start using TLS client certs.

2014-11-13 22:16:45 -08:00

vagrant

Get Vagrant to start using TLS client certs.

2014-11-13 22:16:45 -08:00

vsphere

Fix monitoring setup script.

2014-11-13 16:43:05 -05:00

kube-down.sh

Fix monitoring setup script.

2014-11-13 16:43:05 -05:00

kube-env.sh

AWS support draft

2014-11-10 13:32:52 -08:00

kube-push.sh

Set shell options for reliability.

2014-10-10 12:33:36 -07:00

kube-up.sh

Use Heapster as an in-built monitoring solution for Kubernetes in GCE.

2014-11-07 00:47:56 +00:00

kube-util.sh

Vagrant now using pre-built binaries.

2014-10-10 12:30:12 -07:00

kubecfg.sh

Get Vagrant to start using TLS client certs.

2014-11-13 22:16:45 -08:00

kubectl.sh

Get Vagrant to start using TLS client certs.

2014-11-13 22:16:45 -08:00

validate-cluster.sh

Update scripts to expect versioned output in templates.

2014-11-07 16:47:22 -08:00