diff --git a/OWNERS b/OWNERS new file mode 100644 index 0000000000..247d39ea5e --- /dev/null +++ b/OWNERS @@ -0,0 +1,7 @@ +assignees: +- lavalamp +- smarterclayton +- janetkuo +- pwittrock +- kelseyhightower +- jaredbhatti diff --git a/docs/admin/OWNERS b/docs/admin/OWNERS new file mode 100644 index 0000000000..498d076a5f --- /dev/null +++ b/docs/admin/OWNERS @@ -0,0 +1,4 @@ +assignees: +- derekwaynecarr +- mikedanese + diff --git a/docs/admin/accessing-the-api.md b/docs/admin/accessing-the-api.md index d18d30bfd1..92380ded3f 100644 --- a/docs/admin/accessing-the-api.md +++ b/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. diff --git a/docs/admin/admission-controllers.md b/docs/admin/admission-controllers.md index 9072522ac2..a99b44f339 100644 --- a/docs/admin/admission-controllers.md +++ b/docs/admin/admission-controllers.md @@ -1,4 +1,12 @@ --- +assignees: +- bprashanth +- davidopp +- derekwaynecarr +- erictune +- janetkuo +- thockin + --- * TOC diff --git a/docs/admin/authentication.md b/docs/admin/authentication.md index 52b5bf925d..d003aabb61 100644 --- a/docs/admin/authentication.md +++ b/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. diff --git a/docs/admin/authorization.md b/docs/admin/authorization.md index 312bbb1d05..e683dc1deb 100644 --- a/docs/admin/authorization.md +++ b/docs/admin/authorization.md @@ -1,4 +1,8 @@ --- +assignees: +- erictune +- lavalamp + --- In Kubernetes, authorization happens as a separate step from authentication. diff --git a/docs/admin/cluster-components.md b/docs/admin/cluster-components.md index 2e7e663f42..c1bcae8577 100644 --- a/docs/admin/cluster-components.md +++ b/docs/admin/cluster-components.md @@ -1,4 +1,7 @@ --- +assignees: +- lavalamp + --- This document outlines the various binary components that need to run to diff --git a/docs/admin/cluster-large.md b/docs/admin/cluster-large.md index be05cb627f..6df6bca474 100644 --- a/docs/admin/cluster-large.md +++ b/docs/admin/cluster-large.md @@ -1,4 +1,8 @@ --- +assignees: +- davidopp +- lavalamp + --- diff --git a/docs/admin/cluster-management.md b/docs/admin/cluster-management.md index f133f06983..1be4fc8a02 100644 --- a/docs/admin/cluster-management.md +++ b/docs/admin/cluster-management.md @@ -1,4 +1,8 @@ --- +assignees: +- lavalamp +- thockin + --- * TOC diff --git a/docs/admin/cluster-troubleshooting.md b/docs/admin/cluster-troubleshooting.md index 22d461cd70..8bab089ce6 100644 --- a/docs/admin/cluster-troubleshooting.md +++ b/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 diff --git a/docs/admin/daemons.md b/docs/admin/daemons.md index 2e50d8ef9b..be3137bc93 100644 --- a/docs/admin/daemons.md +++ b/docs/admin/daemons.md @@ -1,4 +1,7 @@ --- +assignees: +- erictune + --- * TOC diff --git a/docs/admin/dns.md b/docs/admin/dns.md index 9bf60e8bba..bdd0848cf9 100644 --- a/docs/admin/dns.md +++ b/docs/admin/dns.md @@ -1,4 +1,9 @@ --- +assignees: +- ArtfulCoder +- davidopp +- lavalamp + --- ## Introduction diff --git a/docs/admin/etcd.md b/docs/admin/etcd.md index f17b555cd8..14b36a33be 100644 --- a/docs/admin/etcd.md +++ b/docs/admin/etcd.md @@ -1,4 +1,7 @@ --- +assignees: +- lavalamp + --- diff --git a/docs/admin/federation/OWNERS b/docs/admin/federation/OWNERS new file mode 100644 index 0000000000..321cd31a2c --- /dev/null +++ b/docs/admin/federation/OWNERS @@ -0,0 +1,4 @@ +assignees: +- mml +- nikhiljindal + diff --git a/docs/admin/federation/index.md b/docs/admin/federation/index.md index fc077ec839..76e08cf90b 100644 --- a/docs/admin/federation/index.md +++ b/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. diff --git a/docs/admin/garbage-collection.md b/docs/admin/garbage-collection.md index 81aeb772c0..d608687400 100644 --- a/docs/admin/garbage-collection.md +++ b/docs/admin/garbage-collection.md @@ -1,4 +1,8 @@ --- +assignees: +- dalanlan +- mikedanese + --- * TOC diff --git a/docs/admin/high-availability/OWNERS b/docs/admin/high-availability/OWNERS new file mode 100644 index 0000000000..0ebc2894ee --- /dev/null +++ b/docs/admin/high-availability/OWNERS @@ -0,0 +1,4 @@ +assignees: +- davidopp +- lavalamp + diff --git a/docs/admin/high-availability/index.md b/docs/admin/high-availability/index.md index d7932e47ca..1074bdeb17 100644 --- a/docs/admin/high-availability/index.md +++ b/docs/admin/high-availability/index.md @@ -1,4 +1,8 @@ ---- +--- +assignees: +- mwhahaha +- stp-ip + --- ## Introduction diff --git a/docs/admin/index.md b/docs/admin/index.md index 1fc64186ea..4df7fb3375 100644 --- a/docs/admin/index.md +++ b/docs/admin/index.md @@ -1,4 +1,8 @@ --- +assignees: +- davidopp +- lavalamp + --- The cluster admin guide is for anyone creating or administering a Kubernetes cluster. diff --git a/docs/admin/kube-apiserver.md b/docs/admin/kube-apiserver.md index 43fe66d37c..350727c61f 100644 --- a/docs/admin/kube-apiserver.md +++ b/docs/admin/kube-apiserver.md @@ -1,4 +1,8 @@ --- +assignees: +- bgrant0607 +- nikhiljindal + --- ## kube-apiserver diff --git a/docs/admin/kube-controller-manager.md b/docs/admin/kube-controller-manager.md index 70a1e576d4..02648408da 100644 --- a/docs/admin/kube-controller-manager.md +++ b/docs/admin/kube-controller-manager.md @@ -1,4 +1,8 @@ --- +assignees: +- bprashanth +- mqliang + --- ## kube-controller-manager diff --git a/docs/admin/kube-proxy.md b/docs/admin/kube-proxy.md index ff2a5af980..feb9143a8f 100644 --- a/docs/admin/kube-proxy.md +++ b/docs/admin/kube-proxy.md @@ -1,4 +1,7 @@ --- +assignees: +- thockin + --- ## kube-proxy diff --git a/docs/admin/kube-scheduler.md b/docs/admin/kube-scheduler.md index e0f6e35fa6..3470241d88 100644 --- a/docs/admin/kube-scheduler.md +++ b/docs/admin/kube-scheduler.md @@ -1,4 +1,8 @@ --- +assignees: +- davidopp +- mikedanese + --- ## kube-scheduler diff --git a/docs/admin/kubelet.md b/docs/admin/kubelet.md index ac88581046..e065c696b9 100644 --- a/docs/admin/kubelet.md +++ b/docs/admin/kubelet.md @@ -1,4 +1,9 @@ --- +assignees: +- bprashanth +- derekwaynecarr +- mikedanese + --- ## kubelet diff --git a/docs/admin/limitrange/OWNERS b/docs/admin/limitrange/OWNERS new file mode 100644 index 0000000000..1dac6f1017 --- /dev/null +++ b/docs/admin/limitrange/OWNERS @@ -0,0 +1,4 @@ +assignees: +- derekwaynecarr +- janetkuo + diff --git a/docs/admin/limitrange/index.md b/docs/admin/limitrange/index.md index 7c89b3058b..f38737981d 100644 --- a/docs/admin/limitrange/index.md +++ b/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 -$ kubectl create namespace limit-example -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: - -```shell +```shell +$ kubectl create namespace limit-example +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: + +```shell $ kubectl get namespaces -NAME STATUS AGE -default Active 51s -limit-example Active 45s -``` - +NAME STATUS AGE +default Active 51s +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. -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: - -```shell +``` + +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. +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 $ kubectl get pods --namespace=limit-example -NAME READY STATUS RESTARTS AGE -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. - -``` shell +NAME READY STATUS RESTARTS AGE +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. + +``` shell $ kubectl get pods nginx-2040093540-s8vzu --namespace=limit-example -o yaml | grep resources -C 8 - resourceVersion: "57" - selfLink: /api/v1/namespaces/limit-example/pods/nginx-2040093540-ivimu - uid: 67b20741-f53b-11e5-b066-64510658e388 -spec: - containers: - - image: nginx - imagePullPolicy: Always - name: nginx - resources: - limits: - cpu: 300m - memory: 200Mi - requests: - cpu: 200m - memory: 100Mi - terminationMessagePath: /dev/termination-log - volumeMounts: -``` - + resourceVersion: "57" + selfLink: /api/v1/namespaces/limit-example/pods/nginx-2040093540-ivimu + uid: 67b20741-f53b-11e5-b066-64510658e388 +spec: + containers: + - image: nginx + imagePullPolicy: Always + name: nginx + resources: + limits: + cpu: 300m + memory: 200Mi + requests: + cpu: 200m + memory: 100Mi + terminationMessagePath: /dev/termination-log + 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: - -```shell +``` + +Now look at the Pod's resources field: + +```shell $ kubectl get pods valid-pod --namespace=limit-example -o yaml | grep -C 6 resources - uid: 3b1bfd7a-f53c-11e5-b066-64510658e388 -spec: - containers: - - image: gcr.io/google_containers/serve_hostname - imagePullPolicy: Always - name: kubernetes-serve-hostname - resources: - limits: - cpu: "1" - memory: 512Mi - requests: - cpu: "1" - memory: 512Mi -``` - + uid: 3b1bfd7a-f53c-11e5-b066-64510658e388 +spec: + containers: + - image: gcr.io/google_containers/serve_hostname + imagePullPolicy: Always + name: kubernetes-serve-hostname + resources: + limits: + cpu: "1" + memory: 512Mi + requests: + cpu: "1" + 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 -default Active 12m -``` - +NAME STATUS AGE +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. diff --git a/docs/admin/master-node-communication.md b/docs/admin/master-node-communication.md index 1d40b265f6..8ed0e3dc82 100644 --- a/docs/admin/master-node-communication.md +++ b/docs/admin/master-node-communication.md @@ -1,4 +1,9 @@ --- +assignees: +- dchen1107 +- laushinka +- roberthbailey + --- * TOC diff --git a/docs/admin/multi-cluster.md b/docs/admin/multi-cluster.md index e549a4d3ca..6359782409 100644 --- a/docs/admin/multi-cluster.md +++ b/docs/admin/multi-cluster.md @@ -1,4 +1,7 @@ --- +assignees: +- davidopp + --- You may want to set up multiple Kubernetes clusters, both to diff --git a/docs/admin/multiple-schedulers.md b/docs/admin/multiple-schedulers.md index a481831e50..8ba152ac04 100644 --- a/docs/admin/multiple-schedulers.md +++ b/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/). diff --git a/docs/admin/multiple-schedulers/OWNERS b/docs/admin/multiple-schedulers/OWNERS new file mode 100644 index 0000000000..3941099ffc --- /dev/null +++ b/docs/admin/multiple-schedulers/OWNERS @@ -0,0 +1,4 @@ +assignees: +- davidopp +- madhusudancs + diff --git a/docs/admin/multiple-zones.md b/docs/admin/multiple-zones.md index f7a6223b50..e5d1367862 100644 --- a/docs/admin/multiple-zones.md +++ b/docs/admin/multiple-zones.md @@ -1,4 +1,9 @@ --- +assignees: +- jlowdermilk +- justinsb +- quinton-hoole + --- ## Introduction diff --git a/docs/admin/namespaces/OWNERS b/docs/admin/namespaces/OWNERS new file mode 100644 index 0000000000..1dac6f1017 --- /dev/null +++ b/docs/admin/namespaces/OWNERS @@ -0,0 +1,4 @@ +assignees: +- derekwaynecarr +- janetkuo + diff --git a/docs/admin/namespaces/index.md b/docs/admin/namespaces/index.md index c9f51280ad..95780559e3 100644 --- a/docs/admin/namespaces/index.md +++ b/docs/admin/namespaces/index.md @@ -1,4 +1,8 @@ --- +assignees: +- derekwaynecarr +- janetkuo + --- A Namespace is a mechanism to partition resources created by users into diff --git a/docs/admin/namespaces/walkthrough.md b/docs/admin/namespaces/walkthrough.md index e3b87c7f65..2a3e6298ea 100644 --- a/docs/admin/namespaces/walkthrough.md +++ b/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. diff --git a/docs/admin/network-plugins.md b/docs/admin/network-plugins.md index 5b41c0e310..ee85126961 100644 --- a/docs/admin/network-plugins.md +++ b/docs/admin/network-plugins.md @@ -1,4 +1,9 @@ --- +assignees: +- dcbw +- freehan +- thockin + --- * TOC diff --git a/docs/admin/networking.md b/docs/admin/networking.md index 8032bdf601..cd8aaa09cf 100644 --- a/docs/admin/networking.md +++ b/docs/admin/networking.md @@ -1,4 +1,8 @@ --- +assignees: +- lavalamp +- thockin + --- Kubernetes approaches networking somewhat differently than Docker does by diff --git a/docs/admin/node-problem.md b/docs/admin/node-problem.md index 5dc2d4cb52..ab09a78dfc 100644 --- a/docs/admin/node-problem.md +++ b/docs/admin/node-problem.md @@ -1,4 +1,8 @@ --- +assignees: +- Random-Liu +- dchen1107 + --- * TOC diff --git a/docs/admin/node.md b/docs/admin/node.md index afae4454d6..1f1c89b4cb 100644 --- a/docs/admin/node.md +++ b/docs/admin/node.md @@ -1,4 +1,9 @@ --- +assignees: +- caesarxuchao +- dchen1107 +- lavalamp + --- * TOC diff --git a/docs/admin/out-of-resource.md b/docs/admin/out-of-resource.md index 2b85f486d5..16b8cc9e1e 100644 --- a/docs/admin/out-of-resource.md +++ b/docs/admin/out-of-resource.md @@ -1,4 +1,9 @@ --- +assignees: +- derekwaynecarr +- vishh +- timstclair + --- * TOC diff --git a/docs/admin/ovs-networking.md b/docs/admin/ovs-networking.md index f5a279339a..7a8f89506c 100644 --- a/docs/admin/ovs-networking.md +++ b/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. diff --git a/docs/admin/resourcequota/OWNERS b/docs/admin/resourcequota/OWNERS new file mode 100644 index 0000000000..dc809362b2 --- /dev/null +++ b/docs/admin/resourcequota/OWNERS @@ -0,0 +1,3 @@ +assignees: +- derekwaynecarr + diff --git a/docs/admin/resourcequota/index.md b/docs/admin/resourcequota/index.md index af96bc538d..d3073848ba 100644 --- a/docs/admin/resourcequota/index.md +++ b/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, diff --git a/docs/admin/resourcequota/walkthrough.md b/docs/admin/resourcequota/walkthrough.md index dcae893d40..4712f7f25a 100644 --- a/docs/admin/resourcequota/walkthrough.md +++ b/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. diff --git a/docs/admin/salt.md b/docs/admin/salt.md index 6210e59055..2cb634d7c6 100644 --- a/docs/admin/salt.md +++ b/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. diff --git a/docs/admin/service-accounts-admin.md b/docs/admin/service-accounts-admin.md index 146f91310b..810f4d7515 100644 --- a/docs/admin/service-accounts-admin.md +++ b/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 diff --git a/docs/admin/static-pods.md b/docs/admin/static-pods.md index a341376c8a..ea9468f31c 100644 --- a/docs/admin/static-pods.md +++ b/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/)!** diff --git a/docs/api-reference/OWNERS b/docs/api-reference/OWNERS new file mode 100644 index 0000000000..cca5435e84 --- /dev/null +++ b/docs/api-reference/OWNERS @@ -0,0 +1,5 @@ +assignees: +- bgrant0607 +- caesarxuchao +- pmorie + diff --git a/docs/api-reference/autoscaling/OWNERS b/docs/api-reference/autoscaling/OWNERS new file mode 100644 index 0000000000..815e01e661 --- /dev/null +++ b/docs/api-reference/autoscaling/OWNERS @@ -0,0 +1,6 @@ +assignees: +- bgrant0607 +- caesarxuchao +- fgrzadkowski +- smarterclayton + diff --git a/docs/api-reference/batch/OWNERS b/docs/api-reference/batch/OWNERS new file mode 100644 index 0000000000..859974e212 --- /dev/null +++ b/docs/api-reference/batch/OWNERS @@ -0,0 +1,6 @@ +assignees: +- bgrant0607 +- caesarxuchao +- gmarek +- smarterclayton + diff --git a/docs/api-reference/extensions/OWNERS b/docs/api-reference/extensions/OWNERS new file mode 100644 index 0000000000..f0dea3903c --- /dev/null +++ b/docs/api-reference/extensions/OWNERS @@ -0,0 +1,6 @@ +assignees: +- bgrant0607 +- caesarxuchao +- madhusudancs +- pmorie + diff --git a/docs/api-reference/v1/OWNERS b/docs/api-reference/v1/OWNERS new file mode 100644 index 0000000000..71582ee6a4 --- /dev/null +++ b/docs/api-reference/v1/OWNERS @@ -0,0 +1,6 @@ +assignees: +- bgrant0607 +- caesarxuchao +- nikhiljindal +- pmorie + diff --git a/docs/api-reference/v1/definitions.md b/docs/api-reference/v1/definitions.md index 05dfc063cf..dddff20bf7 100644 --- a/docs/api-reference/v1/definitions.md +++ b/docs/api-reference/v1/definitions.md @@ -1,3 +1,7 @@ --- +assignees: +- bgrant0607 +- caesarxuchao + --- {% include v1.3/v1-definitions.html %} diff --git a/docs/api-reference/v1/operations.md b/docs/api-reference/v1/operations.md index 32b4629e25..e0241125ba 100644 --- a/docs/api-reference/v1/operations.md +++ b/docs/api-reference/v1/operations.md @@ -1,3 +1,7 @@ --- +assignees: +- bgrant0607 +- caesarxuchao + --- {% include v1.3/v1-operations.html %} diff --git a/docs/api.md b/docs/api.md index ab8a6a3953..aa9aea1d7f 100644 --- a/docs/api.md +++ b/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/). diff --git a/docs/getting-started-guides/OWNERS b/docs/getting-started-guides/OWNERS new file mode 100644 index 0000000000..a1e101ce43 --- /dev/null +++ b/docs/getting-started-guides/OWNERS @@ -0,0 +1,4 @@ +assignees: +- errordeveloper +- pires + diff --git a/docs/getting-started-guides/aws.md b/docs/getting-started-guides/aws.md index 4b5f642ad8..20a310f57f 100644 --- a/docs/getting-started-guides/aws.md +++ b/docs/getting-started-guides/aws.md @@ -1,4 +1,9 @@ --- +assignees: +- JamesDeFabia +- justinsb +- lavalamp + --- * TOC diff --git a/docs/getting-started-guides/azure.md b/docs/getting-started-guides/azure.md index 47050db1c9..bb01c8641d 100644 --- a/docs/getting-started-guides/azure.md +++ b/docs/getting-started-guides/azure.md @@ -1,4 +1,8 @@ --- +assignees: +- colemickens +- jeffmendoza + --- * TOC diff --git a/docs/getting-started-guides/binary_release.md b/docs/getting-started-guides/binary_release.md index 7280e7b89f..d3b2886f87 100644 --- a/docs/getting-started-guides/binary_release.md +++ b/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. diff --git a/docs/getting-started-guides/centos/OWNERS b/docs/getting-started-guides/centos/OWNERS new file mode 100644 index 0000000000..3ff2ad25b0 --- /dev/null +++ b/docs/getting-started-guides/centos/OWNERS @@ -0,0 +1,5 @@ +assignees: +- coolsvap +- lavalamp +- thockin + diff --git a/docs/getting-started-guides/centos/centos_manual_config.md b/docs/getting-started-guides/centos/centos_manual_config.md index f2bc49099f..eeca62036c 100644 --- a/docs/getting-started-guides/centos/centos_manual_config.md +++ b/docs/getting-started-guides/centos/centos_manual_config.md @@ -1,4 +1,9 @@ --- +assignees: +- coolsvap +- lavalamp +- thockin + --- * TOC diff --git a/docs/getting-started-guides/clc.md b/docs/getting-started-guides/clc.md index 3e9b3f0858..637d2707e5 100644 --- a/docs/getting-started-guides/clc.md +++ b/docs/getting-started-guides/clc.md @@ -1,4 +1,8 @@ --- +assignees: +- JamesDeFabia +- ckleban + --- * TOC {: toc} diff --git a/docs/getting-started-guides/cloudstack.md b/docs/getting-started-guides/cloudstack.md index 313c97de65..2361a4fd79 100644 --- a/docs/getting-started-guides/cloudstack.md +++ b/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. diff --git a/docs/getting-started-guides/coreos/OWNERS b/docs/getting-started-guides/coreos/OWNERS new file mode 100644 index 0000000000..a6c2c1b164 --- /dev/null +++ b/docs/getting-started-guides/coreos/OWNERS @@ -0,0 +1,5 @@ +assignees: +- AntonioMeireles +- errordeveloper +- pires + diff --git a/docs/getting-started-guides/coreos/bare_metal_calico.md b/docs/getting-started-guides/coreos/bare_metal_calico.md index 06ca2697a7..2447fe8f90 100644 --- a/docs/getting-started-guides/coreos/bare_metal_calico.md +++ b/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). diff --git a/docs/getting-started-guides/coreos/bare_metal_offline.md b/docs/getting-started-guides/coreos/bare_metal_offline.md index 9f2bec9320..8c71617163 100644 --- a/docs/getting-started-guides/coreos/bare_metal_offline.md +++ b/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. diff --git a/docs/getting-started-guides/coreos/coreos_multinode_cluster.md b/docs/getting-started-guides/coreos/coreos_multinode_cluster.md index cc786e3ec4..9939a6960c 100644 --- a/docs/getting-started-guides/coreos/coreos_multinode_cluster.md +++ b/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. diff --git a/docs/getting-started-guides/coreos/index.md b/docs/getting-started-guides/coreos/index.md index 59fe04a1f2..6eab664c1c 100644 --- a/docs/getting-started-guides/coreos/index.md +++ b/docs/getting-started-guides/coreos/index.md @@ -1,4 +1,8 @@ --- +assignees: +- JamesDeFabia +- johscheuer + --- * TOC diff --git a/docs/getting-started-guides/dcos.md b/docs/getting-started-guides/dcos.md index 442c485bf9..43c6d28e36 100644 --- a/docs/getting-started-guides/dcos.md +++ b/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). diff --git a/docs/getting-started-guides/docker-multinode/OWNERS b/docs/getting-started-guides/docker-multinode/OWNERS new file mode 100644 index 0000000000..687339adf0 --- /dev/null +++ b/docs/getting-started-guides/docker-multinode/OWNERS @@ -0,0 +1,5 @@ +assignees: +- dalanlan +- dchen1107 +- resouer + diff --git a/docs/getting-started-guides/docker.md b/docs/getting-started-guides/docker.md index a6893f27e7..4046045559 100644 --- a/docs/getting-started-guides/docker.md +++ b/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.** diff --git a/docs/getting-started-guides/fedora/OWNERS b/docs/getting-started-guides/fedora/OWNERS new file mode 100644 index 0000000000..26456cebf2 --- /dev/null +++ b/docs/getting-started-guides/fedora/OWNERS @@ -0,0 +1,5 @@ +assignees: +- aveshagarwal +- eparis +- thockin + diff --git a/docs/getting-started-guides/fedora/fedora-calico.md b/docs/getting-started-guides/fedora/fedora-calico.md index a73b7e23bc..d8f983ec18 100644 --- a/docs/getting-started-guides/fedora/fedora-calico.md +++ b/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. diff --git a/docs/getting-started-guides/fedora/fedora_ansible_config.md b/docs/getting-started-guides/fedora/fedora_ansible_config.md index 57532a4fa5..aa439f07b0 100644 --- a/docs/getting-started-guides/fedora/fedora_ansible_config.md +++ b/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. diff --git a/docs/getting-started-guides/fedora/fedora_manual_config.md b/docs/getting-started-guides/fedora/fedora_manual_config.md index 9872275b6c..238498d18c 100644 --- a/docs/getting-started-guides/fedora/fedora_manual_config.md +++ b/docs/getting-started-guides/fedora/fedora_manual_config.md @@ -1,4 +1,9 @@ --- +assignees: +- aveshagarwal +- eparis +- thockin + --- * TOC diff --git a/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md b/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md index 8de2e9dc4e..4c89d85e90 100644 --- a/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md +++ b/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md @@ -1,4 +1,9 @@ --- +assignees: +- dchen1107 +- erictune +- thockin + --- * TOC {:toc} diff --git a/docs/getting-started-guides/gce.md b/docs/getting-started-guides/gce.md index e3bbb8f6e5..a8b3a38a5e 100644 --- a/docs/getting-started-guides/gce.md +++ b/docs/getting-started-guides/gce.md @@ -1,4 +1,10 @@ --- +assignees: +- brendandburns +- jbeda +- mikedanese +- thockin + --- diff --git a/docs/getting-started-guides/index.md b/docs/getting-started-guides/index.md index 404191e62d..59857a03f2 100644 --- a/docs/getting-started-guides/index.md +++ b/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 diff --git a/docs/getting-started-guides/juju.md b/docs/getting-started-guides/juju.md index ac7ceef8d0..d85c4b99c5 100644 --- a/docs/getting-started-guides/juju.md +++ b/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 diff --git a/docs/getting-started-guides/libvirt-coreos.md b/docs/getting-started-guides/libvirt-coreos.md index 0b4d677a1f..eb16ee8a01 100644 --- a/docs/getting-started-guides/libvirt-coreos.md +++ b/docs/getting-started-guides/libvirt-coreos.md @@ -1,4 +1,9 @@ --- +assignees: +- erictune +- idvoretskyi +- lhuard1A + --- * TOC diff --git a/docs/getting-started-guides/locally.md b/docs/getting-started-guides/locally.md index cad7f6b586..afa71ea936 100644 --- a/docs/getting-started-guides/locally.md +++ b/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.** diff --git a/docs/getting-started-guides/logging-elasticsearch.md b/docs/getting-started-guides/logging-elasticsearch.md index 515e981ab7..2141cfbc6d 100644 --- a/docs/getting-started-guides/logging-elasticsearch.md +++ b/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 diff --git a/docs/getting-started-guides/logging.md b/docs/getting-started-guides/logging.md index 84801d45fa..47bb5236b9 100644 --- a/docs/getting-started-guides/logging.md +++ b/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. diff --git a/docs/getting-started-guides/meanstack.md b/docs/getting-started-guides/meanstack.md index c758ed00fd..c3dbdf984a 100644 --- a/docs/getting-started-guides/meanstack.md +++ b/docs/getting-started-guides/meanstack.md @@ -1,4 +1,8 @@ --- +assignees: +- glnds +- paulzim + --- **By: Sandeep Dinesh** - _July 29, 2015_ diff --git a/docs/getting-started-guides/mesos-docker.md b/docs/getting-started-guides/mesos-docker.md index 5067c0ba72..eb9ccbc0ad 100644 --- a/docs/getting-started-guides/mesos-docker.md +++ b/docs/getting-started-guides/mesos-docker.md @@ -1,4 +1,8 @@ --- +assignees: +- jdef +- karlkfi + --- diff --git a/docs/getting-started-guides/mesos/OWNERS b/docs/getting-started-guides/mesos/OWNERS index 7cdb4cdb49..769585a3f1 100644 --- a/docs/getting-started-guides/mesos/OWNERS +++ b/docs/getting-started-guides/mesos/OWNERS @@ -1,3 +1,6 @@ assignees: - - jdef - - karlkfi +- jdef +- nak3 +- sttts +- thockin + diff --git a/docs/getting-started-guides/mesos/index.md b/docs/getting-started-guides/mesos/index.md index 059122c497..b5c6f9932f 100644 --- a/docs/getting-started-guides/mesos/index.md +++ b/docs/getting-started-guides/mesos/index.md @@ -1,4 +1,9 @@ --- +assignees: +- JamesDeFabia +- jdef +- mikebrow + --- * TOC diff --git a/docs/getting-started-guides/minikube.md b/docs/getting-started-guides/minikube.md index 5e61caa967..b2c9b8a776 100644 --- a/docs/getting-started-guides/minikube.md +++ b/docs/getting-started-guides/minikube.md @@ -1,4 +1,9 @@ --- +assignees: +- dlorenc +- janetkuo +- jlowdermilk + --- * TOC diff --git a/docs/getting-started-guides/openstack-heat.md b/docs/getting-started-guides/openstack-heat.md index ae1684bb81..f4b259a2b5 100644 --- a/docs/getting-started-guides/openstack-heat.md +++ b/docs/getting-started-guides/openstack-heat.md @@ -1,4 +1,11 @@ --- +assignees: +- elsonrodriguez +- idvoretskyi +- ohtake +- xsgordon +- zreigz + --- * TOC diff --git a/docs/getting-started-guides/ovirt.md b/docs/getting-started-guides/ovirt.md index e1ebe7e67a..d22b36fe0f 100644 --- a/docs/getting-started-guides/ovirt.md +++ b/docs/getting-started-guides/ovirt.md @@ -1,4 +1,8 @@ --- +assignees: +- caesarxuchao +- erictune + --- * TOC diff --git a/docs/getting-started-guides/photon-controller.md b/docs/getting-started-guides/photon-controller.md index c3482dc654..9878ca898a 100644 --- a/docs/getting-started-guides/photon-controller.md +++ b/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 diff --git a/docs/getting-started-guides/rackspace.md b/docs/getting-started-guides/rackspace.md index a91187275e..d71438bb1e 100644 --- a/docs/getting-started-guides/rackspace.md +++ b/docs/getting-started-guides/rackspace.md @@ -1,4 +1,8 @@ --- +assignees: +- doublerr +- erictune + --- * Supported Version: v0.18.1 diff --git a/docs/getting-started-guides/rkt/OWNERS b/docs/getting-started-guides/rkt/OWNERS new file mode 100644 index 0000000000..578ee5b700 --- /dev/null +++ b/docs/getting-started-guides/rkt/OWNERS @@ -0,0 +1,5 @@ +assignees: +- joshix +- lavalamp +- yifan-gu + diff --git a/docs/getting-started-guides/rkt/index.md b/docs/getting-started-guides/rkt/index.md index 00d5764c83..8bc25d07e3 100644 --- a/docs/getting-started-guides/rkt/index.md +++ b/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. diff --git a/docs/getting-started-guides/rkt/notes.md b/docs/getting-started-guides/rkt/notes.md index 30a022dc24..658d5de2a9 100644 --- a/docs/getting-started-guides/rkt/notes.md +++ b/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. diff --git a/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md index eb59ff061e..a4fd03e643 100644 --- a/docs/getting-started-guides/scratch.md +++ b/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 diff --git a/docs/getting-started-guides/ubuntu-calico.md b/docs/getting-started-guides/ubuntu-calico.md index 678b9b8388..bfa92be2bb 100644 --- a/docs/getting-started-guides/ubuntu-calico.md +++ b/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). diff --git a/docs/getting-started-guides/ubuntu.md b/docs/getting-started-guides/ubuntu.md index 1643841d53..236a6d9e6e 100644 --- a/docs/getting-started-guides/ubuntu.md +++ b/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 diff --git a/docs/getting-started-guides/vagrant.md b/docs/getting-started-guides/vagrant.md index b72649b581..09bd4a20c9 100644 --- a/docs/getting-started-guides/vagrant.md +++ b/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.** diff --git a/docs/getting-started-guides/vsphere.md b/docs/getting-started-guides/vsphere.md index 0e98968bda..3b2d34d324 100644 --- a/docs/getting-started-guides/vsphere.md +++ b/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 diff --git a/docs/hellonode.md b/docs/hellonode.md index 146e6452f7..41da09d274 100755 --- a/docs/hellonode.md +++ b/docs/hellonode.md @@ -1,4 +1,9 @@ --- +assignees: +- dchen1107 +- juretta +- pwittrock + --- * TOC diff --git a/docs/index.md b/docs/index.md index da6febb315..84a2f5c08a 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,4 +1,8 @@ --- +assignees: +- bgrant0607 +- thockin + ---