From 8cec9c3987d75899ad5e0588a5d7ca169d76dd97 Mon Sep 17 00:00:00 2001 From: Dhilip Date: Thu, 31 Aug 2017 01:20:14 +0530 Subject: [PATCH] fix a broken link --- docs/concepts/cluster-administration/logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/cluster-administration/logging.md b/docs/concepts/cluster-administration/logging.md index 42475f124f..ad90ba9e4e 100644 --- a/docs/concepts/cluster-administration/logging.md +++ b/docs/concepts/cluster-administration/logging.md @@ -60,7 +60,7 @@ so that logs don't consume all available storage on the node. Kubernetes currently is not responsible for rotating logs, but rather a deployment tool should set up a solution to address that. For example, in Kubernetes clusters, deployed by the `kube-up.sh` script, -there is a [`logrotate`](http://www.linuxcommand.org/man_pages/logrotate8.html) +there is a [`logrotate`](https://linux.die.net/man/8/logrotate) tool configured to run each hour. You can also set up a container runtime to rotate application's logs automatically, e.g. by using Docker's `log-opt`. In the `kube-up.sh` script, the latter approach is used for COS image on GCP,