k3s/cluster/saltbase/pillar
Justin Santa Barbara 4d2c580781 AWS kube-up: Add support for wily
vivid is technically no longer supported now, so we should support
wily.
2016-02-17 10:45:21 -05:00
..
README.md Fix some problems: 2015-10-16 21:29:05 +08:00
cluster-params.sls
docker-images.sls run kube-proxy in a static pod 2015-11-18 16:52:10 -08:00
logging.sls
mine.sls
privilege.sls allow privileged pods 2015-09-22 13:44:08 -07:00
systemd.sls AWS kube-up: Add support for wily 2016-02-17 10:45:21 -05:00
top.sls Salt: support systemd (don't assume Redhat <=> systemd) 2015-07-03 01:40:15 -04:00

README.md

The SaltStack pillar data is partially statically derived from the contents of this directory. The bulk of the pillars are hard to perceive from browsing this directory, though, because they are written into cluster-params.sls at cluster inception.

  • cluster-params.sls is generated entirely at cluster inception. See e.g. configure-vm.sh
  • docker-images.sls stores the Docker tags of the current Docker-wrapped server binaries, twiddling by the Salt install script
  • logging.sls defines the cluster log level
  • mine.sls: defines the variables shared across machines in the Salt mine. It is starting to be largely deprecated in use, and is totally unavailable on GCE, which runs standalone.
  • privilege.sls defines whether privileged containers are allowed.
  • top.sls defines which pillars are active across the cluster.

Future work

Document the current pillars across providers

Analytics