Files

k8s-merge-robot 17c3f19c64 Merge pull request #21737 from FujitsuEnablingSoftwareTechnologyGmbH/openstack-provider

Automatic merge from submit-queue

Openstack provider

Our pull request delivers solution to create Kubernetes cluster on the top of OpenStack. Heat OpenStack Orchestration engine describes the infrastructure for Kubernetes cluster. CentoOS images are used for Kubernetes host machines.

We tested our solution with DevStack and Citycloud provider.

We believe that our solution will fill the gap that which is on the market.

<!-- Reviewable:start -->
---
This change is [<img src="http://reviewable.k8s.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](http://reviewable.k8s.io/reviews/kubernetes/kubernetes/21737)
<!-- Reviewable:end -->

2016-05-10 23:56:47 -07: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

Merge pull request #21737 from FujitsuEnablingSoftwareTechnologyGmbH/openstack-provider

2016-05-10 23:56:47 -07: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: