From 34e3432bbaa122f0033ac080ea9aa38298f6307e Mon Sep 17 00:00:00 2001 From: Dawn Chen Date: Tue, 14 Jul 2015 17:47:34 -0700 Subject: [PATCH] Known issue for logging.md --- docs/user-guide/logging.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/user-guide/logging.md b/docs/user-guide/logging.md index 6dea0026920..f8fa3c6b466 100644 --- a/docs/user-guide/logging.md +++ b/docs/user-guide/logging.md @@ -90,6 +90,10 @@ describes how to ingest cluster level logs into Elasticsearch and view them usin Cluster level logging only collects the standard output and standard error output of the applications running in containers. The guide [Collecting log files within containers with Fluentd](../../contrib/logging/fluentd-sidecar-gcp/README.md) explains how the log files of applications can also be ingested into Google Cloud logging. +## Known issues + +Kubernetes does log rotation for kubernetes components and docker containers. The command `kubectl logs` currently only read the latest logs, not all historical ones. + [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/user-guide/logging.md?pixel)]()