github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/cluster/saltbase
History
k8s-merge-robot 5debaf7b88 Merge pull request #27253 from luxas/latest_hyperkube_addons 
Automatic merge from submit-queue

Update to dnsmasq:1.3 and make hyperkube always use the latest addons

This bumps dnsmasq to a version that works on all architectures: https://github.com/kubernetes/contrib/pull/1192 (which have to be pushed first indeed)

Also I removed the manifests in hyperkube addons in favor for machine-generated ones, which will avoid mistakes.

This one is required for `v1.3`, so it has to be cherrypicked I think...

It makes docker and docker-multinode addons work again...
(Yes, we'll probably get rid of docker in favor for minikube, but we'll have to have it in this release at least)

@girishkalele @thockin @ArtfulCoder @david-mcmahon @bgrant0607 @mikedanese
 		2016-06-19 22:19:09 -07:00
..
pillar AWS kube-up: Add support for wily 2016-02-17 10:45:21 -05:00
reactor
…
salt Merge pull request #27253 from luxas/latest_hyperkube_addons 2016-06-19 22:19:09 -07:00
README.md declare azure/ubuntu/saltstack bankruptcy 2015-10-16 18:21:21 -07:00
install.sh don't ship kube-registry-proxy and pause in tars. 2016-04-05 07:32:07 -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, and Ubuntu-on-AWS. (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 in grains.cloud; the documentation in this tree uses this same shorthand for convenience.

See more:

Analytics