Adding OWNERS for docs.

OWNERS

@@ -0,0 +1,7 @@
+assignees:
+- lavalamp
+- smarterclayton
+- janetkuo
+- pwittrock
+- kelseyhightower
+- jaredbhatti

docs/admin/OWNERS

@@ -0,0 +1,4 @@
+assignees:
+- derekwaynecarr
+- mikedanese
+

docs/admin/accessing-the-api.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- bgrant0607
+- erictune
+- lavalamp
+
 ---
 
 This document describes how access to the Kubernetes API is controlled.

docs/admin/admission-controllers.md

@@ -1,4 +1,12 @@
 ---
+assignees:
+- bprashanth
+- davidopp
+- derekwaynecarr
+- erictune
+- janetkuo
+- thockin
+
 ---
 
 * TOC

docs/admin/authentication.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- erictune
+- lavalamp
+- yifan-gu
+
 ---
 
 Kubernetes uses client certificates, tokens, or http basic auth to authenticate users for API calls.

docs/admin/authorization.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- erictune
+- lavalamp
+
 ---
 
 In Kubernetes, authorization happens as a separate step from authentication.

docs/admin/cluster-components.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- lavalamp
+
 ---
 
 This document outlines the various binary components that need to run to

docs/admin/cluster-large.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- davidopp
+- lavalamp
+
 ---
 
 

docs/admin/cluster-management.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- lavalamp
+- thockin
+
 ---
 
 * TOC

docs/admin/cluster-troubleshooting.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- davidopp
+
 ---
 
 This doc is about cluster troubleshooting; we assume you have already ruled out your application as the root cause of the

docs/admin/daemons.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- erictune
+
 ---
 
 * TOC

docs/admin/dns.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- ArtfulCoder
+- davidopp
+- lavalamp
+
 ---
 
 ## Introduction

docs/admin/etcd.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- lavalamp
+
 ---
 
 

docs/admin/federation/OWNERS

@@ -0,0 +1,4 @@
+assignees:
+- mml
+- nikhiljindal
+

docs/admin/federation/index.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- mml
+- nikhiljindal
+
 ---
 This guide explains how to set up cluster federation that lets us control multiple Kubernetes clusters.
 

docs/admin/garbage-collection.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- dalanlan
+- mikedanese
+
 ---
 
 * TOC

docs/admin/high-availability/OWNERS

@@ -0,0 +1,4 @@
+assignees:
+- davidopp
+- lavalamp
+

docs/admin/high-availability/index.md

@@ -1,4 +1,8 @@
----
+---
+assignees:
+- mwhahaha
+- stp-ip
+
 ---
 
 ## Introduction

docs/admin/index.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- davidopp
+- lavalamp
+
 ---
 
 The cluster admin guide is for anyone creating or administering a Kubernetes cluster.

docs/admin/kube-apiserver.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- bgrant0607
+- nikhiljindal
+
 ---
 
 ## kube-apiserver

docs/admin/kube-controller-manager.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- bprashanth
+- mqliang
+
 ---
 
 ## kube-controller-manager

docs/admin/kube-proxy.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- thockin
+
 ---
 
 ## kube-proxy

docs/admin/kube-scheduler.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- davidopp
+- mikedanese
+
 ---
 
 ## kube-scheduler

docs/admin/kubelet.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- bprashanth
+- derekwaynecarr
+- mikedanese
+
 ---
 
 ## kubelet

docs/admin/limitrange/OWNERS

@@ -0,0 +1,4 @@
+assignees:
+- derekwaynecarr
+- janetkuo
+

docs/admin/limitrange/index.md

@@ -1,5 +1,9 @@
----
+---
----
+assignees:
+- derekwaynecarr
+- janetkuo
+
+---
 
 By default, pods run with unbounded CPU and memory limits.  This means that any pod in the
 system will be able to consume as much CPU and memory on the node that executes the pod.
@@ -40,32 +44,32 @@ This example will work in a custom namespace to demonstrate the concepts involve
 
 Let's create a new namespace called limit-example:
 
-```shell
+```shell
-$ kubectl create namespace limit-example
+$ kubectl create namespace limit-example
-namespace "limit-example" created
+namespace "limit-example" created
-```
+```
-
+
-Note that `kubectl` commands will print the type and name of the resource created or mutated, which can then be used in subsequent commands: 
+Note that `kubectl` commands will print the type and name of the resource created or mutated, which can then be used in subsequent commands: 
-
+
-```shell
+```shell
 $ kubectl get namespaces
-NAME            STATUS    AGE
+NAME            STATUS    AGE
-default         Active    51s
+default         Active    51s
-limit-example   Active    45s
+limit-example   Active    45s
-```
+```
-
+
 ## Step 2: Apply a limit to the namespace
 
 Let's create a simple limit in our namespace.
 
-```shell
+```shell
 $ kubectl create -f docs/admin/limitrange/limits.yaml --namespace=limit-example
 limitrange "mylimits" created
-```
+```
-
+
 Let's describe the limits that we have imposed in our namespace.
 
-```shell
+```shell
 $ kubectl describe limits mylimits --namespace=limit-example
 Name:   mylimits
 Namespace:  limit-example
@@ -75,8 +79,8 @@ Pod         cpu           200m     2        -                    -
 Pod         memory        6Mi      1Gi      -                    -                  -
 Container   cpu           100m     2        200m                 300m               -
 Container   memory        3Mi      1Gi      100Mi                200Mi              -
-```
+```
-
+
 In this scenario, we have said the following:
 
 1. If a max constraint is specified for a resource (2 CPU and 1Gi memory in this case), then a limit
@@ -103,108 +107,108 @@ of creation explaining why.
 Let's first spin up a [Deployment](/docs/user-guide/deployments) that creates a single container Pod to demonstrate
 how default values are applied to each pod.
 
-```shell
+```shell
 $ kubectl run nginx --image=nginx --replicas=1 --namespace=limit-example
 deployment "nginx" created
-```
+```
-
+
-Note that `kubectl run` creates a Deployment named "nginx" on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead.
+Note that `kubectl run` creates a Deployment named "nginx" on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead.
-If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/user-guide/kubectl/kubectl_run/) for more details. 
+If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/user-guide/kubectl/kubectl_run/) for more details. 
-The Deployment manages 1 replica of single container Pod. Let's take a look at the Pod it manages. First, find the name of the Pod:
+The Deployment manages 1 replica of single container Pod. Let's take a look at the Pod it manages. First, find the name of the Pod:
-
+
-```shell 
+```shell 
 $ kubectl get pods --namespace=limit-example
-NAME                     READY     STATUS    RESTARTS   AGE
+NAME                     READY     STATUS    RESTARTS   AGE
-nginx-2040093540-s8vzu   1/1       Running   0          11s
+nginx-2040093540-s8vzu   1/1       Running   0          11s
-```
+```
-
+
-Let's print this Pod with yaml output format (using `-o yaml` flag), and then `grep` the `resources` field. Note that your pod name will be different. 
+Let's print this Pod with yaml output format (using `-o yaml` flag), and then `grep` the `resources` field. Note that your pod name will be different. 
-
+
-``` shell
+``` shell
 $ kubectl get pods nginx-2040093540-s8vzu --namespace=limit-example -o yaml | grep resources -C 8
-  resourceVersion: "57"
+  resourceVersion: "57"
-  selfLink: /api/v1/namespaces/limit-example/pods/nginx-2040093540-ivimu
+  selfLink: /api/v1/namespaces/limit-example/pods/nginx-2040093540-ivimu
-  uid: 67b20741-f53b-11e5-b066-64510658e388
+  uid: 67b20741-f53b-11e5-b066-64510658e388
-spec:
+spec:
-  containers:
+  containers:
-  - image: nginx
+  - image: nginx
-    imagePullPolicy: Always
+    imagePullPolicy: Always
-    name: nginx
+    name: nginx
-    resources:
+    resources:
-      limits:
+      limits:
-        cpu: 300m
+        cpu: 300m
-        memory: 200Mi
+        memory: 200Mi
-      requests:
+      requests:
-        cpu: 200m
+        cpu: 200m
-        memory: 100Mi
+        memory: 100Mi
-    terminationMessagePath: /dev/termination-log
+    terminationMessagePath: /dev/termination-log
-    volumeMounts:
+    volumeMounts:
-```
+```
-
+
 Note that our nginx container has picked up the namespace default cpu and memory resource *limits* and *requests*.
 
 Let's create a pod that exceeds our allowed limits by having it have a container that requests 3 cpu cores.
 
-```shell
+```shell
 $ kubectl create -f docs/admin/limitrange/invalid-pod.yaml --namespace=limit-example
 Error from server: error when creating "docs/admin/limitrange/invalid-pod.yaml": Pod "invalid-pod" is forbidden: [Maximum cpu usage per Pod is 2, but limit is 3., Maximum cpu usage per Container is 2, but limit is 3.]
-```
+```
-
+
 Let's create a pod that falls within the allowed limit boundaries.
 
-```shell
+```shell
 $ kubectl create -f docs/admin/limitrange/valid-pod.yaml --namespace=limit-example
 pod "valid-pod" created
-```
+```
-
+
-Now look at the Pod's resources field: 
+Now look at the Pod's resources field: 
-
+
-```shell
+```shell
 $ kubectl get pods valid-pod --namespace=limit-example -o yaml | grep -C 6 resources
-  uid: 3b1bfd7a-f53c-11e5-b066-64510658e388
+  uid: 3b1bfd7a-f53c-11e5-b066-64510658e388
-spec:
+spec:
-  containers:
+  containers:
-  - image: gcr.io/google_containers/serve_hostname
+  - image: gcr.io/google_containers/serve_hostname
-    imagePullPolicy: Always
+    imagePullPolicy: Always
-    name: kubernetes-serve-hostname
+    name: kubernetes-serve-hostname
-    resources:
+    resources:
-      limits:
+      limits:
-        cpu: "1"
+        cpu: "1"
-        memory: 512Mi
+        memory: 512Mi
-      requests:
+      requests:
-        cpu: "1"
+        cpu: "1"
-        memory: 512Mi
+        memory: 512Mi
-```
+```
-
+
 Note that this pod specifies explicit resource *limits* and *requests* so it did not pick up the namespace
 default values.
 
 Note: The *limits* for CPU resource are enforced in the default Kubernetes setup on the physical node
 that runs the container unless the administrator deploys the kubelet with the folllowing flag:
 
-```shell
+```shell
 $ kubelet --help
 Usage of kubelet
 ....
   --cpu-cfs-quota[=true]: Enable CPU CFS quota enforcement for containers that specify CPU limits
 $ kubelet --cpu-cfs-quota=false ...
-```
+```
-
+
 ## Step 4: Cleanup
 
 To remove the resources used by this example, you can just delete the limit-example namespace.
 
-```shell
+```shell
 $ kubectl delete namespace limit-example
 namespace "limit-example" deleted
 $ kubectl get namespaces
-NAME            STATUS        AGE
+NAME            STATUS        AGE
-default         Active        12m
+default         Active        12m
-```
+```
-
+
 ## Summary
 
 Cluster operators that want to restrict the amount of resources a single container or pod may consume
 are able to define allowable ranges per Kubernetes namespace.  In the absence of any explicit assignments,
 the Kubernetes system is able to apply default resource *limits* and *requests* if desired in order to
-constrain the amount of resource a pod consumes on a node.
+constrain the amount of resource a pod consumes on a node.

docs/admin/master-node-communication.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- dchen1107
+- laushinka
+- roberthbailey
+
 ---
 
 * TOC

docs/admin/multi-cluster.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- davidopp
+
 ---
 
 You may want to set up multiple Kubernetes clusters, both to

docs/admin/multiple-schedulers.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- davidopp
+- madhusudancs
+
 ---
 
 Kubernetes ships with a default scheduler that is described [here](/docs/admin/kube-scheduler/).

docs/admin/multiple-schedulers/OWNERS

@@ -0,0 +1,4 @@
+assignees:
+- davidopp
+- madhusudancs
+

docs/admin/multiple-zones.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- jlowdermilk
+- justinsb
+- quinton-hoole
+
 ---
 
 ## Introduction

docs/admin/namespaces/OWNERS

@@ -0,0 +1,4 @@
+assignees:
+- derekwaynecarr
+- janetkuo
+

docs/admin/namespaces/index.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- derekwaynecarr
+- janetkuo
+
 ---
 
 A Namespace is a mechanism to partition resources created by users into

docs/admin/namespaces/walkthrough.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- derekwaynecarr
+- janetkuo
+
 ---
 
 Kubernetes _namespaces_ help different projects, teams, or customers to share a Kubernetes cluster.

docs/admin/network-plugins.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- dcbw
+- freehan
+- thockin
+
 ---
 
 * TOC

docs/admin/networking.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- lavalamp
+- thockin
+
 ---
 
 Kubernetes approaches networking somewhat differently than Docker does by

docs/admin/node-problem.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- Random-Liu
+- dchen1107
+
 ---
 
 * TOC

docs/admin/node.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- caesarxuchao
+- dchen1107
+- lavalamp
+
 ---
 
 * TOC

docs/admin/out-of-resource.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- derekwaynecarr
+- vishh
+- timstclair
+
 ---
 
 * TOC

docs/admin/ovs-networking.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- lavalamp
+- thockin
+
 ---
 
 This document describes how OpenVSwitch is used to setup networking between pods across nodes.

docs/admin/resourcequota/OWNERS

@@ -0,0 +1,3 @@
+assignees:
+- derekwaynecarr
+

docs/admin/resourcequota/index.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- derekwaynecarr
+
 ---
 
 When several users or teams share a cluster with a fixed number of nodes,

docs/admin/resourcequota/walkthrough.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- derekwaynecarr
+- janetkuo
+
 ---
 
 This example demonstrates a typical setup to control for resource usage in a namespace.

docs/admin/salt.md

@@ -1,5 +1,9 @@
----
+---
----
+assignees:
+- davidopp
+- lavalamp
+
+---
 
 The Kubernetes cluster can be configured using Salt.
 
@@ -13,11 +17,11 @@ The **salt-minion** service runs on the kubernetes-master and each kubernetes-no
 
 Each salt-minion service is configured to interact with the **salt-master** service hosted on the kubernetes-master via the **master.conf** file [(except on GCE)](#standalone-salt-configuration-on-gce).
 
-```shell
+```shell
 [root@kubernetes-master] $ cat /etc/salt/minion.d/master.conf
 master: kubernetes-master
-```
+```
-
+
 The salt-master is contacted by each salt-minion and depending upon the machine information presented, the salt-master will provision the machine as either a kubernetes-master or kubernetes-node with all the required capabilities needed to run Kubernetes.
 
 If you are running the Vagrant based environment, the **salt-api** service is running on the kubernetes-master.  It is configured to enable the vagrant user to introspect the salt cluster in order to find out about machines in the Vagrant environment via a REST API.
@@ -34,27 +38,27 @@ All remaining sections that refer to master/minion setups should be ignored for
 
 Security is not enabled on the salt-master, and the salt-master is configured to auto-accept incoming requests from minions.  It is not recommended to use this security configuration in production environments without deeper study.  (In some environments this isn't as bad as it might sound if the salt master port isn't externally accessible and you trust everyone on your network.)
 
-```shell
+```shell
 [root@kubernetes-master] $ cat /etc/salt/master.d/auto-accept.conf
 open_mode: True
 auto_accept: True
-```
+```
-
+
 ## Salt minion configuration
 
 Each minion in the salt cluster has an associated configuration that instructs the salt-master how to provision the required resources on the machine.
 
 An example file is presented below using the Vagrant based environment.
 
-```shell
+```shell
 [root@kubernetes-master] $ cat /etc/salt/minion.d/grains.conf
 grains:
   etcd_servers: $MASTER_IP
   cloud: vagrant
   roles:
     - kubernetes-master
-```
+```
-
+
 Each hosting environment has a slightly different grains.conf file that is used to build conditional logic where required in the Salt files.
 
 The following enumerates the set of defined key/value pairs that are supported today.  If you add new ones, please make sure to update this list.
@@ -77,16 +81,16 @@ These keys may be leveraged by the Salt sls files to branch behavior.
 
 In addition, a cluster may be running a Debian based operating system or Red Hat based operating system (Centos, Fedora, RHEL, etc.).  As a result, it's important to sometimes distinguish behavior based on operating system using if branches like the following.
 
-```liquid
+```liquid
 {% raw %}
 {% if grains['os_family'] == 'RedHat' %}
 // something specific to a RedHat environment (Centos, Fedora, RHEL) where you may use yum, systemd, etc.
 {% else %}
 // something specific to Debian environment (apt-get, initd)
-{% endif %}
+{% endif %}
 {% endraw %}
-```
+```
-
+
 ## Best Practices
 
 1.  When configuring default arguments for processes, it's best to avoid the use of EnvironmentFiles (Systemd in Red Hat environments) or init.d files (Debian distributions) to hold default values that should be common across operating system environments.  This helps keep our Salt template files easy to understand for editors who may not be familiar with the particulars of each distribution.

docs/admin/service-accounts-admin.md

@@ -1,4 +1,10 @@
 ---
+assignees:
+- bprashanth
+- davidopp
+- lavalamp
+- liggitt
+
 ---
 
 *This is a Cluster Administrator guide to service accounts.  It assumes knowledge of

docs/admin/static-pods.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- jsafrane
+
 ---
 
 **If you are running clustered Kubernetes and are using static pods to run a pod on every node, you should probably be using a [DaemonSet](/docs/admin/daemons/)!**

docs/api-reference/OWNERS

@@ -0,0 +1,5 @@
+assignees:
+- bgrant0607
+- caesarxuchao
+- pmorie
+

docs/api-reference/autoscaling/OWNERS

@@ -0,0 +1,6 @@
+assignees:
+- bgrant0607
+- caesarxuchao
+- fgrzadkowski
+- smarterclayton
+

docs/api-reference/batch/OWNERS

@@ -0,0 +1,6 @@
+assignees:
+- bgrant0607
+- caesarxuchao
+- gmarek
+- smarterclayton
+

docs/api-reference/extensions/OWNERS

@@ -0,0 +1,6 @@
+assignees:
+- bgrant0607
+- caesarxuchao
+- madhusudancs
+- pmorie
+

docs/api-reference/v1/OWNERS

@@ -0,0 +1,6 @@
+assignees:
+- bgrant0607
+- caesarxuchao
+- nikhiljindal
+- pmorie
+

docs/api-reference/v1/definitions.md

@@ -1,3 +1,7 @@
 ---
+assignees:
+- bgrant0607
+- caesarxuchao
+
 ---
 {% include v1.3/v1-definitions.html %}

docs/api-reference/v1/operations.md

@@ -1,3 +1,7 @@
 ---
+assignees:
+- bgrant0607
+- caesarxuchao
+
 ---
 {% include v1.3/v1-operations.html %}

docs/api.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- bgrant0607
+- erictune
+- lavalamp
+
 ---
 
 Primary system and API concepts are documented in the [User guide](/docs/user-guide/).

docs/getting-started-guides/OWNERS

@@ -0,0 +1,4 @@
+assignees:
+- errordeveloper
+- pires
+

docs/getting-started-guides/aws.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- JamesDeFabia
+- justinsb
+- lavalamp
+
 ---
 
 * TOC

docs/getting-started-guides/azure.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- colemickens
+- jeffmendoza
+
 ---
 
 * TOC

docs/getting-started-guides/binary_release.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- david-mcmahon
+- jbeda
+
 ---
 
 You can either build a release from sources or download a pre-built release.  If you do not plan on developing Kubernetes itself, we suggest a pre-built release. 

docs/getting-started-guides/centos/OWNERS

@@ -0,0 +1,5 @@
+assignees:
+- coolsvap
+- lavalamp
+- thockin
+

docs/getting-started-guides/centos/centos_manual_config.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- coolsvap
+- lavalamp
+- thockin
+
 ---
 
 * TOC

docs/getting-started-guides/clc.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- JamesDeFabia
+- ckleban
+
 ---
 * TOC
 {: toc}

docs/getting-started-guides/cloudstack.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- lavalamp
+- thockin
+
 ---
 
 CloudStack is a software to build public and private clouds based on hardware virtualization principles (traditional IaaS). To deploy Kubernetes on CloudStack there are several possibilities depending on the Cloud being used and what images are made available. [Exoscale](http://exoscale.ch) for instance makes a [CoreOS](http://coreos.com) template available, therefore instructions to deploy Kubernetes on coreOS can be used. CloudStack also has a vagrant plugin available, hence Vagrant could be used to deploy Kubernetes either using the existing shell provisioner or using new Salt based recipes.

docs/getting-started-guides/coreos/OWNERS

@@ -0,0 +1,5 @@
+assignees:
+- AntonioMeireles
+- errordeveloper
+- pires
+

docs/getting-started-guides/coreos/bare_metal_calico.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- caseydavenport
+
 ---
 
 This document describes how to deploy Kubernetes with Calico networking on _bare metal_ CoreOS. For more information on Project Calico, visit [projectcalico.org](http://projectcalico.org) and the [calico-containers repository](https://github.com/projectcalico/calico-containers).

docs/getting-started-guides/coreos/bare_metal_offline.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- erictune
+- jeffbean
+- thockin
+
 ---
 
 Deploy a CoreOS running Kubernetes environment. This particular guide is made to help those in an OFFLINE system, wither for testing a POC before the real deal, or you are restricted to be totally offline for your applications.

docs/getting-started-guides/coreos/coreos_multinode_cluster.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- dchen1107
+- pires
+
 ---
 
 Use the [master.yaml](/docs/getting-started-guides/coreos/cloud-configs/master.yaml) and [node.yaml](/docs/getting-started-guides/coreos/cloud-configs/node.yaml) cloud-configs to provision a multi-node Kubernetes cluster.

docs/getting-started-guides/coreos/index.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- JamesDeFabia
+- johscheuer
+
 ---
 
 * TOC

docs/getting-started-guides/dcos.md

@@ -1,4 +1,7 @@
 ---
+assignees:
+- karlkfi
+
 ---
 
 This guide will walk you through installing [Kubernetes-Mesos](https://github.com/mesosphere/kubernetes-mesos) on [Datacenter Operating System (DCOS)](https://mesosphere.com/product/) with the [DCOS CLI](https://github.com/mesosphere/dcos-cli) and operating Kubernetes with the [DCOS Kubectl plugin](https://github.com/mesosphere/dcos-kubectl).

docs/getting-started-guides/docker-multinode/OWNERS

@@ -0,0 +1,5 @@
+assignees:
+- dalanlan
+- dchen1107
+- resouer
+

docs/getting-started-guides/docker.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- asridharan
+- brendandburns
+- fgrzadkowski
+
 ---
 
 **Stop. This guide has been superseded by [Minikube](../minikube/) which is the recommended method of running Kubernetes on your local machine.**

docs/getting-started-guides/fedora/OWNERS

@@ -0,0 +1,5 @@
+assignees:
+- aveshagarwal
+- eparis
+- thockin
+

docs/getting-started-guides/fedora/fedora-calico.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- alexhersh
+- caesarxuchao
+- caseydavenport
+
 ---
 
 This guide will walk you through the process of getting a Kubernetes Fedora cluster running on Digital Ocean with networking powered by Calico networking.

docs/getting-started-guides/fedora/fedora_ansible_config.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- aveshagarwal
+- erictune
+
 ---
 
 Configuring Kubernetes on Fedora via Ansible offers a simple way to quickly create a clustered environment with little effort.

docs/getting-started-guides/fedora/fedora_manual_config.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- aveshagarwal
+- eparis
+- thockin
+
 ---
 
 * TOC

docs/getting-started-guides/fedora/flannel_multi_node_cluster.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- dchen1107
+- erictune
+- thockin
+
 ---
 * TOC
 {:toc}

docs/getting-started-guides/gce.md

@@ -1,4 +1,10 @@
 ---
+assignees:
+- brendandburns
+- jbeda
+- mikedanese
+- thockin
+
 ---
 
 

docs/getting-started-guides/index.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- brendandburns
+- erictune
+- mikedanese
+
 ---
 
 Kubernetes can run on a range of platforms, from your laptop, to VMs on a cloud provider, to rack of

docs/getting-started-guides/juju.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- caesarxuchao
+- erictune
+- mbruzek
+
 ---
 
 [Juju](https://jujucharms.com/docs/2.0/about-juju) encapsulates the 

docs/getting-started-guides/libvirt-coreos.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- erictune
+- idvoretskyi
+- lhuard1A
+
 ---
 
 * TOC

docs/getting-started-guides/locally.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- erictune
+- mikedanese
+- thockin
+
 ---
 
 **Stop. This guide has been superseded by [Minikube](../minikube/) which is the recommended method of running Kubernetes on your local machine.**

docs/getting-started-guides/logging-elasticsearch.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- lavalamp
+- satnam6502
+
 ---
 
 On the Google Compute Engine (GCE) platform, the default logging support targets

docs/getting-started-guides/logging.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- lavalamp
+- satnam6502
+
 ---
 
 A Kubernetes cluster will typically be humming along running many system and application pods. How does the system administrator collect, manage and query the logs of the system pods? How does a user query the logs of their application which is composed of many pods which may be restarted or automatically generated by the Kubernetes system? These questions are addressed by the Kubernetes **cluster level logging** services.

docs/getting-started-guides/meanstack.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- glnds
+- paulzim
+
 ---
 
 **By: Sandeep Dinesh** - _July 29, 2015_

docs/getting-started-guides/mesos-docker.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- jdef
+- karlkfi
+
 ---
 
 

docs/getting-started-guides/mesos/OWNERS

@@ -1,3 +1,6 @@
 assignees:
-  - jdef
+- jdef
-  - karlkfi
+- nak3
+- sttts
+- thockin
+

docs/getting-started-guides/mesos/index.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- JamesDeFabia
+- jdef
+- mikebrow
+
 ---
 
 * TOC

docs/getting-started-guides/minikube.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- dlorenc
+- janetkuo
+- jlowdermilk
+
 ---
 
 * TOC

docs/getting-started-guides/openstack-heat.md

@@ -1,4 +1,11 @@
 ---
+assignees:
+- elsonrodriguez
+- idvoretskyi
+- ohtake
+- xsgordon
+- zreigz
+
 ---
 
 * TOC

docs/getting-started-guides/ovirt.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- caesarxuchao
+- erictune
+
 ---
 
 * TOC

docs/getting-started-guides/photon-controller.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- AlainRoy
+- bprashanth
+
 ---
 
 The example below creates a Kubernetes cluster using VMware's Photon

docs/getting-started-guides/rackspace.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- doublerr
+- erictune
+
 ---
 
 * Supported Version: v0.18.1

docs/getting-started-guides/rkt/OWNERS

@@ -0,0 +1,5 @@
+assignees:
+- joshix
+- lavalamp
+- yifan-gu
+

docs/getting-started-guides/rkt/index.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- joshix
+- lavalamp
+- yifan-gu
+
 ---
 
 This document describes how to run Kubernetes using [rkt](https://github.com/coreos/rkt) as the container runtime.

docs/getting-started-guides/rkt/notes.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- dchen1107
+- yifan-gu
+
 ---
 
 The following features either are not supported or have large caveats when using the rkt container runtime. Increasing support for these items and others, including reasonable feature parity with the default container engine, is planned through future releases.

docs/getting-started-guides/scratch.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- erictune
+- lavalamp
+- thockin
+
 ---
 
 This guide is for people who want to craft a custom Kubernetes cluster.  If you

docs/getting-started-guides/ubuntu-calico.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- alexhersh
+- caseydavenport
+
 ---
 
 This document describes how to deploy Kubernetes with Calico networking from scratch on _bare metal_ Ubuntu. For more information on Project Calico, visit [projectcalico.org](http://projectcalico.org) and the [calico-containers repository](https://github.com/projectcalico/calico-containers).

docs/getting-started-guides/ubuntu.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- WIZARD-CXY
+- dalanlan
+- thockin
+
 ---
 
 This document describes how to deploy kubernetes on ubuntu nodes, 1 master and 3 nodes involved

docs/getting-started-guides/vagrant.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- brendandburns
+- derekwaynecarr
+- jbeda
+
 ---
 
 **Stop. This guide has been superseded by [Minikube](../minikube/) which is the recommended method of running Kubernetes on your local machine.**

docs/getting-started-guides/vsphere.md

@@ -1,4 +1,8 @@
 ---
+assignees:
+- erictune
+- jbeda
+
 ---
 
 The example below creates a Kubernetes cluster with 4 worker node Virtual

docs/hellonode.md

@@ -1,4 +1,9 @@
 ---
+assignees:
+- dchen1107
+- juretta
+- pwittrock
+
 ---
 
 * TOC