From 51f12efae93dc5b472778d2f9482f3507e01dc75 Mon Sep 17 00:00:00 2001 From: Eric Ernst Date: Fri, 29 Mar 2019 14:03:59 -0700 Subject: [PATCH] arch: fix dead link api.proto moved, resulting in a broken link. The original link wasn't very useful in the first place, so simply remove. Signed-off-by: Eric Ernst --- design/architecture.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/design/architecture.md b/design/architecture.md index 7e0b1105e..f7d07b490 100644 --- a/design/architecture.md +++ b/design/architecture.md @@ -544,8 +544,7 @@ dedicated master node) calls into a compute kubelet. This kubelet instance is responsible for managing the lifecycle of pods within the nodes and eventually relies on a container runtime to handle execution. The kubelet architecture decouples lifecycle management from container execution through the dedicated -[`gRPC`](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/apis/cri/runtime/v1alpha2/api.proto) -based [Container Runtime Interface (CRI)](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/node/container-runtime-interface-v1.md). +`gRPC` based [Container Runtime Interface (CRI)](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/node/container-runtime-interface-v1.md). In other words, a kubelet is a CRI client and expects a CRI implementation to handle the server side of the interface.