Files

Francois Deppierraz dd786794e9 Expose /etc/pki from host to kube-apiserver and controller-manager

CentOS 7 Core nodes running on OpenStack with an SSL-enabled API
endpoint results in the following error without this patch:

F0425 19:00:58.124520       5 server.go:100] Cloud provider could not be initialized: could not init cloud provider "openstack": Post https://my.openstack.cloud:5000/v2.0/tokens: x509: failed to load system roots and no roots provided

The root cause is that the ca-bundle.crt file is actually a symlink
which points to a directory which wasn't previously exposed.

[root@kubernetesstack-master ~]# ls -l /etc/ssl/certs/ca-bundle.crt
lrwxrwxrwx. 1 root root 49 18 nov 11:02 /etc/ssl/certs/ca-bundle.crt -> /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
[root@kubernetesstack-master ~]#

2016-04-28 23:07:24 +02:00

pillar

AWS kube-up: Add support for wily

2016-02-17 10:45:21 -05:00

reactor

Add ga-beacon analytics to gendocs scripts

2015-05-15 18:56:38 -07:00

salt

Expose /etc/pki from host to kube-apiserver and controller-manager

2016-04-28 23:07:24 +02:00

install.sh

don't ship kube-registry-proxy and pause in tars.

2016-04-05 07:32:07 -07:00

README.md

declare azure/ubuntu/saltstack bankruptcy

2015-10-16 18:21:21 -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: