diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-11-07 18:37:10 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-07 18:37:10 -0800 |
| commit | b3279464dd304a7e67c342b7185fa37ade73cdcc (patch) | |
| tree | 3fc5958bb79cc9e55017f84d6c0c2d70af46676a | |
| parent | 28a20bf9bd963ec2bbe411b72611c2b0b14ee442 (diff) | |
| parent | 3c2faae22267b8f8efb3dc8341b1144e1401032a (diff) | |
Merge pull request #1357 from chenhonggc/kubelet-cri-logging
Automatic merge from submit-queue.
typo
type, `metada ` should be `metadata `.
| -rw-r--r-- | contributors/design-proposals/node/kubelet-cri-logging.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/node/kubelet-cri-logging.md b/contributors/design-proposals/node/kubelet-cri-logging.md index 41c5cc9c..f4e35861 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** |