Files
kubernetes/cluster/saltbase/salt
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
..
2017-08-24 17:49:18 +08:00
2016-12-22 20:15:37 +00:00
2015-12-02 15:21:01 +01:00
2017-08-24 17:49:18 +08:00
2017-08-24 17:49:18 +08:00
2017-08-24 17:49:18 +08:00
2017-08-24 17:49:18 +08:00
2015-08-01 14:32:08 -04:00
2017-08-24 17:49:18 +08:00
2017-05-30 16:55:25 -07:00
2017-05-30 16:55:25 -07:00

This directory forms the base of the main SaltStack configuration. The place to start with any SaltStack configuration is top.sls. However, unless you are particularly keen on reading Jinja templates, the following tables break down what configurations run on what providers. (NB: The _states directory is a special directory included by Salt for ensure blocks, and is only used for the docker config.)

Key: M = Config applies to master, n = config applies to nodes

Config GCE Vagrant AWS Azure
debian-auto-upgrades M n M n M n M n
docker M n M n M n M n
etcd M M M M
generate-cert M M M M
kube-addons M M M M
kube-apiserver M M M M
kube-controller-manager M M M M
kube-proxy n n n n
kube-scheduler M M M M
kubelet M n M n M n M n
logrotate M n n M n M n
supervisord M n M n M n M n
base M n M n M n M n
kube-client-tools M M M M

Analytics