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.
This commit is contained in:
Jerome Petazzoni
2018-11-01 19:42:52 -05:00
parent 4f71074a06
commit d3fac47823
2 changed files with 1 additions and 2 deletions

View File

@@ -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

View File

@@ -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!