From 1e160b9b81055ddd9ddcd1a945761880ebded811 Mon Sep 17 00:00:00 2001 From: Robert Kielty Date: Tue, 30 Jul 2019 17:38:49 +0100 Subject: [PATCH] adds a ref to container-runtimes (#15581) Just added a link to container-runtimes from the k8s docs --- content/en/docs/concepts/workloads/pods/pod-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-overview.md b/content/en/docs/concepts/workloads/pods/pod-overview.md index 81a2b397b5..b14a2aa443 100644 --- a/content/en/docs/concepts/workloads/pods/pod-overview.md +++ b/content/en/docs/concepts/workloads/pods/pod-overview.md @@ -21,7 +21,7 @@ A *Pod* is the basic execution unit of a Kubernetes application--the smallest an A Pod encapsulates an application's container (or, in some cases, multiple containers), storage resources, a unique network IP, and options that govern how the container(s) should run. A Pod represents a unit of deployment: *a single instance of an application in Kubernetes*, which might consist of either a single {{< glossary_tooltip text="container" term_id="container" >}} or a small number of containers that are tightly coupled and that share resources. -[Docker](https://www.docker.com) is the most common container runtime used in a Kubernetes Pod, but Pods support other container runtimes as well. +[Docker](https://www.docker.com) is the most common container runtime used in a Kubernetes Pod, but Pods support other [container runtimes](https://kubernetes.io/docs/setup/production-environment/container-runtimes/) as well. Pods in a Kubernetes cluster can be used in two main ways: