Files

Matt Johnson ce220836c3 Allow for local CNI binaries and configuration files with KUBERNETES_PROVIDER=vagrant.

Files are taken from cluster/network-plugins/{bin,conf} to be consumed within a vagrant kube-up.sh environment.
Paths used for configuration files and the 'cni' name of the network provider are all from the kubernetes documentation, but the actual implementation in the salt automation doesn't seem to exist.

2016-04-04 14:38:00 +01:00

pillar

AWS kube-up: Add support for wily

2016-02-17 10:45:21 -05:00

reactor

Add ga-beacon analytics to gendocs scripts

2015-05-15 18:56:38 -07:00

salt

Allow for local CNI binaries and configuration files with KUBERNETES_PROVIDER=vagrant.

2016-04-04 14:38:00 +01:00

install.sh

Regional registries: Hack the manifests!

2016-03-04 20:00:54 -08:00

README.md

declare azure/ubuntu/saltstack bankruptcy

2015-10-16 18:21:21 -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, and Ubuntu-on-AWS. (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 in grains.cloud; the documentation in this tree uses this same shorthand for convenience.

See more: