Kubed lets you view logs of containers running in Kubernetes, using
kubectl logs under the hood. The most general command for
viewing logs is kubed-logs, which is bound to L in
kubed-prefix-map (see Definition of kubed-prefix-map):
Show logs for containers running in a Kubernetes resource. This command asks you for a resource type and name, and pops up a buffer with the logs of the containers running in that resource.
In resource list buffers that support logs—such as those for pods, deployments, services, and jobs—you can view logs for the resource at point directly:
Show logs for the resource at point (kubed-list-logs). Kubed
opens a new buffer with the log output.
Open a type-specific logs transient menu for the resource at point,
with the resource pre-selected. Kubed also pre-populates the
‘--tail’ and ‘--follow’ options from
kubed-logs-tail-lines and kubed-logs-follow, which you
can adjust before invoking the command. See Transient Menus.
Two user options control the default behavior of these commands:
Number of most recent log lines to fetch and show when displaying Kubernetes logs. The default is 128. Set this option to 0 to show all available log lines without limit.
Whether to follow new log entries when displaying Kubernetes logs.
The default is t.
When Kubed sets up a buffer for displaying logs, it runs the following hook:
List of functions to call, in order, to set up Kubernetes logs
buffers. The default value is (view-mode).