From 3c7f39747c6365a474599213c5dd0130576acdad Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Wed, 5 Dec 2018 17:55:18 -0600 Subject: [PATCH] Mention the kubectl logs -l ... --tail N issue in k8s 1.12 This supersedes #399. There was a bug in Kubernetes 1.12. It was fixed in 1.13. Let's just mention the issue in one brief slide but not add too much extra fluff about it. --- slides/k8s/kubectlrun.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/slides/k8s/kubectlrun.md b/slides/k8s/kubectlrun.md index eb5d711f..2faee4ce 100644 --- a/slides/k8s/kubectlrun.md +++ b/slides/k8s/kubectlrun.md @@ -295,6 +295,24 @@ Unfortunately, `--follow` cannot (yet) be used to stream the logs from multiple --- +class: extra-details + +## `kubectl logs -l ... --tail N` + +- If we run this with Kubernetes 1.12, the last command shows multiple lines + +- This is a regression when `--tail` is used together with `-l`/`--selector` + +- It always shows the last 10 lines of output for each container + + (instead of the number of lines specified on the command line) + +- The problem was fixed in Kubernetes 1.13 + +*See [#70554](https://github.com/kubernetes/kubernetes/issues/70554) for details.* + +--- + ## Aren't we flooding 1.1.1.1? - If you're wondering this, good question!