From f08c6423d95ad385ec573aa0ce49d834bb046873 Mon Sep 17 00:00:00 2001 From: JR Date: Mon, 3 Jul 2017 18:10:22 -0700 Subject: [PATCH] Clarify what is co-located Prior to this change, it was not clear what was co-located/scheduled; pods vs their contents. --- docs/concepts/workloads/pods/pod.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/workloads/pods/pod.md b/docs/concepts/workloads/pods/pod.md index d399ad550d..8d7aa3076e 100644 --- a/docs/concepts/workloads/pods/pod.md +++ b/docs/concepts/workloads/pods/pod.md @@ -17,7 +17,7 @@ managed in Kubernetes. A _pod_ (as in a pod of whales or pea pod) is a group of one or more containers (such as Docker containers), the shared storage for those containers, and -options about how to run the containers. Pods are always co-located and +options about how to run the containers. A pod's contents are always co-located and co-scheduled, and run in a shared context. A pod models an application-specific "logical host" - it contains one or more application containers which are relatively tightly coupled — in a pre-container