k3s/cluster/saltbase/pillar
Jeff Lowdermilk 553f9f822b Add ga-beacon analytics to gendocs scripts
hack/run-gendocs.sh puts ga-beacon analytics link into all md files,
hack/verify-gendocs.sh verifies presence of link.
2015-05-15 18:56:38 -07:00
..
README.md Add ga-beacon analytics to gendocs scripts 2015-05-15 18:56:38 -07:00
cluster-params.sls Vagrant now using pre-built binaries. 2014-10-10 12:30:12 -07:00
docker-images.sls docker image creation 2015-04-02 12:39:12 -07:00
logging.sls Fix up for posix flags 2015-01-15 09:12:19 -08:00
mine.sls Fix regression introduced when moving to standalone salt 2015-03-11 11:06:00 -04:00
privilege.sls Add a salt flag for enabling privileged containers. 2014-09-17 14:25:28 -07:00
top.sls docker image creation 2015-04-02 12:39:12 -07:00

README.md

The SaltStack pillar data is partially statically dervied 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