github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/cluster/saltbase
History
Cheng Xing e21ecc0166 Updated Flexvolume setup mechanisms for COS instance image. 
- If REMOUNT_VOLUME_PLUGIN_DIR is set to true, VOLUME_PLUGIN_DIR is remounted with `exec` option during cluster startup. This allows any writable location to be used as the plugin directory.
- New HostPath added to controller-manager deployment to enable access to volume plugin directory.
- Improved how the default directory is passed to master and node setup.
 		2018-01-08 15:38:51 -08: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 Updated Flexvolume setup mechanisms for COS instance image. 2018-01-08 15:38:51 -08:00
BUILD Replace git_repository with http_archive and use ixdy's fork of bazel tools for pkg_tar 2017-05-03 10:13:06 -07:00
README.md Fix url for Saltstack administration document 2017-09-17 14:46:26 +08:00
install.sh Revert k8s.gcr.io vanity domain 2017-12-22 14:36:16 -08: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:

Analytics