Files

k8s-merge-robot 878d2b2f18 Merge pull request #26625 from sttts/sttts-fix-kube-dns-sed-transform

Automatic merge from submit-queue

Fix sed transformation for new kube-dns yaml

<!--
Checklist for submitting a Pull Request

Please remove this comment block before submitting.

1. Please read our [contributor guidelines](https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md).
2. See our [developer guide](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md).
3. If you want this PR to automatically close an issue when it is merged,
   add `fixes #<issue number>` or `fixes #<issue number>, fixes #<issue number>`
   to close multiple issues (see: https://github.com/blog/1506-closing-issues-via-pull-requests).
4. Follow the instructions for [labeling and writing a release note for this PR](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes) in the block below.
-->

```release-note
* Use the release-note-* labels to set the release note state 
* Clear this block to use the PR title as the release note 
-OR-
* Enter your extended release note here
```


[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/.github/PULL_REQUEST_TEMPLATE.md?pixel)]()

2016-06-02 01:12:53 -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 #26625 from sttts/sttts-fix-kube-dns-sed-transform

2016-06-02 01:12:53 -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: