Files

Kubernetes Submit Queue 1f2f05df4b Merge pull request #39140 from kerneltime/master

Automatic merge from submit-queue

Remove kube-up for vsphere

**What this PR does / why we need it**:
Kube-up for vSphere does not work in master or 1.5 branch due to changes in networking model within kubernetes.
Kube-up is deprecated
Kube-up for vSphere is not being maintained instead the focus is on kubernetes-anywhere.

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: 
fixes https://github.com/kubernetes/kubernetes/issues/37150, fixes https://github.com/kubernetes/kubernetes/issues/36440, fixes https://github.com/kubernetes/kubernetes/issues/27947, fixes https://github.com/kubernetes/kubernetes/issues/24407, fixes https://github.com/kubernetes/kubernetes/issues/22390, fixes https://github.com/kubernetes/kubernetes/issues/14368, fixes https://github.com/kubernetes/kubernetes/issues/14363, fixes https://github.com/kubernetes/kubernetes/issues/3630, fixes https://github.com/kubernetes/kubernetes/issues/22885


**Special notes for your reviewer**:

This is related to https://github.com/kubernetes/kubernetes.github.io/pull/2021

**Release note**:

```release-note
Remove the deprecated vsphere kube-up.
```

2016-12-29 11:38:08 -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

Merge pull request #39140 from kerneltime/master

2016-12-29 11:38:08 -08:00

install.sh

2016-06-29 17:47:36 -07:00

README.md

Implement Azure cloud provider scripts

2016-06-17 23:46:03 -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, 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: