Files
kubernetes/cluster/saltbase/salt
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
..
2017-03-22 16:03:13 -07:00
2017-02-27 16:23:44 +01:00
2017-03-08 11:36:11 -08:00

This directory forms the base of the main SaltStack configuration. The place to start with any SaltStack configuration is top.sls. However, unless you are particularly keen on reading Jinja templates, the following tables break down what configurations run on what providers. (NB: The _states directory is a special directory included by Salt for ensure blocks, and is only used for the docker config.)

Key: M = Config applies to master, n = config applies to nodes

Config GCE Vagrant AWS Azure
debian-auto-upgrades M n M n M n M n
docker M n M n M n M n
etcd M M M M
generate-cert M M M M
kube-addons M M M M
kube-apiserver M M M M
kube-controller-manager M M M M
kube-proxy n n n n
kube-scheduler M M M M
kubelet M n M n M n M n
logrotate M n n M n M n
supervisord M n M n M n M n
nginx M
openvpn-client n
openvpn M
base M n M n M n M n
kube-client-tools M M M M

Analytics