Pod Logs

Including logs from pods in the collected output

The logs collectors can be used to include logs from running pods. This collector can be included multiple times with different label selectors and/or namespaces.


In addition to the shared collector properties, the logs collector accepts the following parameters:

selector (Required)

The selector to use to find matching pods. If this selector returns more than one pod, all matching pods will be collected.

Multiple selectors are possible, but the results are a logical AND, not a logical OR, meaning that the resulting set of pod may not contain the expected results (possibly no results). It is best to use separate collectors to generate individual logs for different service pods.


The pod labels in service1-deployment.yaml:

  name: service1
    app.kubernetes.io/name: service1

The collector YAML in support-bundle.yaml:

    - logs:
          - app.kubernetes.io/name=service1
namespace (Optional)

The namespace to search for the pod selector in. If this is not provided, it will default to the current namespace of the context.

name (Required)

Name will be used to create a folder in the support bundle where logs will be saved. Name can contain slashes to create a path in the support bundle.

containerNames (Optional)

ContainerNames is an array of container names. If specified, logs for each container in the list will be collected. This can be omitted for pods with only one container.

limits (Optional)

Provided to limit the size of the logs. By default, this is set to maxLines: 10000. Either maxAge or maxLines can be provided, but not both.


The duration of the maximum oldest log to include. For duration string format see time.ParseDuration.


The number of lines to include, starting from the newest.

Example Collector Definition

apiVersion: troubleshoot.sh/v1beta2
kind: SupportBundle
  name: sample
    - logs:
          - app=api
        namespace: default
        name: api/container/logs
          - api
          - node
          maxAge: 720h
          maxLines: 1000

Note: troubleshoot.sh/v1beta2 was introduced in preflight and support-bundle krew plugin version 0.9.39 and Kots version 1.19.0. Kots vendors should read the guide to maintain backwards compatibility.

Included resources

When this collector is executed, it will include the following files in a support bundle:


This will be created for each pod that matches the selector.

If any errors are encounted, the following file will be created:


  "failed to get log stream: container node is not valid for pod api-6fd69d8f78-tmtf7"
Edit on GitHub