From 08ef8f205cacc54cd79776db498c6f946d41363f Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Thu, 15 Oct 2020 12:00:00 +0100 Subject: [PATCH] Reinstate link to container concept via glossary This reverts commit 74dee751444b58e0595f4a37fe29c6ebd5f2d30d. --- content/en/docs/concepts/workloads/pods/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/_index.md b/content/en/docs/concepts/workloads/pods/_index.md index 59543acf23..9247cd3a0d 100644 --- a/content/en/docs/concepts/workloads/pods/_index.md +++ b/content/en/docs/concepts/workloads/pods/_index.md @@ -15,7 +15,7 @@ card: _Pods_ are the smallest deployable units of computing that you can create and manage in Kubernetes. A _Pod_ (as in a pod of whales or pea pod) is a group of one or more -[containers](/docs/concepts/containers/), with shared storage/network resources, and a specification +{{< glossary_tooltip text="containers" term_id="container" >}}, with shared storage/network resources, and a specification for 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