Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
Go to file
Justin Santa Barbara 09cb75f3dc Salt: force service provider to systemd if systemd
The version of Salt we're running doesn't do a good job of detecting
systemd.  Inspired by https://github.com/saltstack/salt/issues/13926,
I added a provider-force to the services.

With this change, salt-call -l debug state.highstate succeeds, even for
repeated invocations.

The issue was (probably) benign, but definitely caused noised (e.g. #11297)
2016-03-29 11:01:37 -07:00
CONTRIBUTING.md final commit 2016-03-29 10:27:47 -07:00
LICENSE final commit 2016-03-29 10:27:47 -07:00
README final commit 2016-03-29 10:27:47 -07:00
init.sls Salt: force service provider to systemd if systemd 2016-03-29 11:01:37 -07:00
initd kill child processes of addon-update on stop 2016-03-29 11:01:37 -07:00
kube-addon-update.sh kube-addons: Use python container if python is not found on the machine. 2016-03-29 11:01:37 -07:00
kube-addons.service kube2sky using kubeconfig secret: take 2. Point system secrets at https://kubernetes. Override in clients that can't use DNS. 2016-03-29 10:58:03 -07:00
kube-addons.sh Fix issues with Python3 and bring up a dev cluster 2016-03-29 11:01:37 -07:00
namespace.yaml Move things into a 'kube-system' namespace. 2016-03-29 11:01:23 -07:00

README

# kube-deploy

This is a repository of community maintained Kubernetes cluster deployment automations.