Files

Andy Goldstein d2bc4d0b2e Use shared informers for proxy endpoints and service configs

Use shared informers instead of creating local controllers/reflectors
for the proxy's endpoints and service configs. This allows downstream
integrators to pass in preexisting shared informers to save on memory &
cpu usage.

This also enables the cache mutation detector for kube-proxy for those
presubmit jobs that already turn it on.

2017-04-04 12:51:41 -04:00

pillar

update oscodenames supporting systemd

2016-10-18 09:37:40 -04:00

reactor

Remove kube-up for vsphere

2016-12-22 20:15:37 +00:00

salt

Use shared informers for proxy endpoints and service configs

2017-04-04 12:51:41 -04:00

BUILD

Build release tarballs in bazel and add make bazel-release rule

2017-01-13 16:17:44 -08:00

install.sh

2016-06-29 17:47:36 -07:00

README.md

Implement Azure cloud provider scripts

2016-06-17 23:46:03 -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: