From 3c2faae22267b8f8efb3dc8341b1144e1401032a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=99=88=E5=AE=8F?= Date: Tue, 7 Nov 2017 15:50:08 +0800 Subject: [PATCH] typo --- contributors/design-proposals/node/kubelet-cri-logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/design-proposals/node/kubelet-cri-logging.md b/contributors/design-proposals/node/kubelet-cri-logging.md index 41c5cc9c4..f4e358617 100644 --- a/contributors/design-proposals/node/kubelet-cri-logging.md +++ b/contributors/design-proposals/node/kubelet-cri-logging.md @@ -137,7 +137,7 @@ Because kubelet determines where the logs are stores and can access them directly, this meets requirement (1). As for requirement (2), the log collector can easily extract basic pod metadata (e.g., pod UID, container name) from the paths, and watch the directly for any changes. In the future, we can -extend this by maintaining a metada file in the pod directory. +extend this by maintaining a metadata file in the pod directory. **Log format**