From cc1cdf79dc084ef340a9219b806c0e35e1339156 Mon Sep 17 00:00:00 2001 From: Ahmet Alp Balkan Date: Thu, 20 Apr 2017 10:11:44 -0700 Subject: [PATCH] Fix broken link in architecture.md Signed-off-by: Ahmet Alp Balkan --- contributors/design-proposals/architecture.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/contributors/design-proposals/architecture.md b/contributors/design-proposals/architecture.md index 3dac164e1..28ccc3f61 100644 --- a/contributors/design-proposals/architecture.md +++ b/contributors/design-proposals/architecture.md @@ -213,8 +213,9 @@ agent. Each node runs a container runtime, which is responsible for downloading images and running containers. -Kubelet does not link in the base container runtime. Instead, we're defining a [Container Runtime Interface] -(container-runtime-interface-v1.md) to control the underlying runtime and facilitate pluggability of that layer. +Kubelet does not link in the base container runtime. Instead, we're defining a +[Container Runtime Interface](container-runtime-interface-v1.md) to control the +underlying runtime and facilitate pluggability of that layer. This decoupling is needed in order to maintain clear component boundaries, facilitate testing, and facilitate pluggability. Runtimes supported today, either upstream or by forks, include at least docker (for Linux and Windows), [rkt](https://kubernetes.io/docs/getting-started-guides/rkt/),