kubernetes/cluster/saltbase
Kubernetes Submit Queue 712cb4d3e9 Merge pull request #51737 from MrHohn/kube-proxy-owner
Automatic merge from submit-queue (batch tested with PRs 51553, 51538, 51663, 51069, 51737)

Edit owner files for kube-proxy manifests

**What this PR does / why we need it**: We should have owner file for kube-proxy daemonset manifest.

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

**Special notes for your reviewer**:
/assign @bowei @thockin 
cc @dnardo @freehan @nicksardo 

**Release note**:

```release-note
NONE
```
2017-09-02 21:58:06 -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 #51737 from MrHohn/kube-proxy-owner 2017-09-02 21:58:06 -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 Remove "All rights reserved" from all the headers. 2016-06-29 17:47:36 -07:00
README.md Update docs/ URLs to point to proper locations 2017-06-05 22:13:54 -07:00

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:

Analytics