History

Kubernetes Submit Queue 223c167d66 Merge pull request #37139 from MrHohn/addon-manager-6.0 Automatic merge from submit-queue Bumps up Addon Manager to v6.0 with full support of kubectl apply Below images are built and pushed: - gcr.io/google-containers/kube-addon-manager:v6.0 - gcr.io/google-containers/kube-addon-manager-amd64:v6.0 - gcr.io/google-containers/kube-addon-manager-arm:v6.0 - gcr.io/google-containers/kube-addon-manager-arm64:v6.0 - gcr.io/google-containers/kube-addon-manager-ppc64le:v6.0 The actual change made is upgrade kubectl version from `v1.5.0-alpha.1` to `v1.5.0-beta.1`, which is released today. @mikedanese @saad-ali This need to get into 1.5 because Addon Manager v6.0-alpha.1 (currently in used) does not have full support of `kubectl apply --prune`.		2016-11-29 14:19:05 -08:00
..
pillar	update oscodenames supporting systemd	2016-10-18 09:37:40 -04:00
reactor	Add ga-beacon analytics to gendocs scripts	2015-05-15 18:56:38 -07:00
salt	Merge pull request #37139 from MrHohn/addon-manager-6.0	2016-11-29 14:19:05 -08:00
README.md	Implement Azure cloud provider scripts	2016-06-17 23:46:03 -07:00
install.sh	Remove "All rights reserved" from all the headers.	2016-06-29 17:47:36 -07:00

README.md

SaltStack configuration

This is the root of the SaltStack configuration for Kubernetes. A high level overview for the Kubernetes SaltStack configuration can be found in the docs tree.

This SaltStack configuration currently applies to default configurations for Debian-on-GCE, Fedora-on-Vagrant, Ubuntu-on-AWS and Ubuntu-on-Azure. (That doesn't mean it can't be made to apply to an arbitrary configuration, but those are only the in-tree OS/IaaS combinations supported today.) As you peruse the configuration, these are shorthanded as gce, vagrant, aws, azure-legacy in grains.cloud; the documentation in this tree uses this same shorthand for convenience.

See more: