Files

Kubernetes Submit Queue 855551dc80 Merge pull request #51250 from dixudx/bump_cni_v0.6.0

Automatic merge from submit-queue (batch tested with PRs 53106, 52193, 51250, 52449, 53861). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

bump CNI to v0.6.0

**What this PR does / why we need it**:

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #49480

**Special notes for your reviewer**:
/assign @luxas @bboreham @feiskyer 

**Release note**:

```release-note
bump CNI to v0.6.0
```

2017-10-16 14:47:23 -07: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 #51250 from dixudx/bump_cni_v0.6.0

2017-10-16 14:47:23 -07:00

BUILD

Replace git_repository with http_archive and use ixdy's fork of bazel tools for pkg_tar

2017-05-03 10:13:06 -07:00

install.sh

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

README.md

Fix url for Saltstack administration document

2017-09-17 14:46:26 +08: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: