From d3fac478236921e7408e539027c2a2824a8db79d Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Thu, 1 Nov 2018 19:42:52 -0500 Subject: [PATCH] kubectl logs -l ... --tail ... is buggy. (It always returns 10 lines of output instead of the requested number.) This works around the problem, by adding extra explanations of the issue and providing a shell function as a workaround. See kubernetes/kubernetes#70554 for details. --- slides/k8s/daemonset.md | 2 +- slides/k8s/kubectlrun.md | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/slides/k8s/daemonset.md b/slides/k8s/daemonset.md index 82a8a18e..ba113b0a 100644 --- a/slides/k8s/daemonset.md +++ b/slides/k8s/daemonset.md @@ -285,7 +285,7 @@ It appears that *all the pods* are serving requests at the moment. - We mentioned earlier that regression affecting `kubectl logs` ... - (see [#70443](https://github.com/kubernetes/kubernetes/issues/70554) for more details) + (see [#70554](https://github.com/kubernetes/kubernetes/issues/70554) for more details) - Let's work around the issue by executing `kubectl logs` one pod at a time diff --git a/slides/k8s/kubectlrun.md b/slides/k8s/kubectlrun.md index 5e49e66a..dbe9229c 100644 --- a/slides/k8s/kubectlrun.md +++ b/slides/k8s/kubectlrun.md @@ -314,6 +314,5 @@ Unfortunately, `--follow` cannot (yet) be used to stream the logs from multiple (Source: https://blog.cloudflare.com/announcing-1111/) - - It's very unlikely that our concerted pings manage to produce even a modest blip at Cloudflare's NOC!