Sysdig Documentation

Runtime Support: CRI-O and Containerd

By default, Sysdig agents deployed in Kubernetes automatically detect metadata from containerd and CRI-O (in addition to Docker), as long as the prerequisites are fulfilled.

After reviewing the information on this page, continue with the Sysdig agent installation steps: Kubernetes Agent Installation Steps.

Containerd Support

As of agent version 0.88.1, the Sysdig agent will automatically detect containerd metadata (as well as any Docker metadata) in your environment, as long as the Prerequisites are fulfilled.

Prerequisites

  • Agent version: Sysdig agent version 0.88.1 or higher

    NOTE: If you are upgrading from an earlier version of the agent, you must also download the latest sysdig-agent-daemonset-v2.yaml from GitHub.

  • Configuration parameter: In the agent config file, new_k8s: true must be set.

    See Enable Kube State Metrics and Cluster Name below for details on editing the config file.

  • Kubernetes-only: The containerd API must support CRI (a Kubernetes runtime interface).

Results in the Sysdig Monitor UI

If the Sysdig agent detects containerd metadata, it will be reported in the front end as follows:

  • Explore/Dashboard views: The icon next to container-specific items (container.name, container.id, etc.) shows whether it's a Docker or containerd object.

    373574647.jpg
  • Spotlight: Updated for containerd display.

  • Events: Containerd events die and oom are enabled by default.

    Events create and exit are also supported.

    373574641.jpg

CRI-O Support

The Sysdig agent will automatically detect CRI-O metadata (as well as any Docker and/or containerd metadata) in your environment, as long as the Prerequisites are fulfilled.

Prerequisites

  • Platform version: Sysdig SaaS March 2019or higher

  • Agent version: Sysdig agent 0.89.4 March 27, 2019or higher0.89.4 March 27, 2019

    NOTE: If you are upgrading from an earlier version of the agent, you must also download the latest sysdig-agent-daemonset-v2.yamlfrom GitHub.

  • Configuration parameter: In the agent config file, new_k8s: true must be set.

    See Enable Kube State Metrics and Cluster Name below for details on editing the config file.

  • Kubernetes-only: The API must support CRI (a Kubernetes runtime interface).

Results in the Sysdig Monitor UI

  • Events: There are no CRI-O events, so the Events pane remains unchanged.

  • Explore/Dashboard views: The icon next to container-specific items (container.name, container.id, etc.) shows CRI-O type.

  • Supported Metrics: By default, the same metrics are supported for CRI-O as for Docker and containerd, except for image id ( container.image.id ).

Enable Image ID Metrics with cri: extra_queries

Note

As of agent version 0.92.1, this setting is enabled by default.

To enable image id metrics, edit the agent configuration file dragent.yaml to contain the following:

cri:
  extra_queries: true

See Understanding the Agent Config Files for more information on editing dragent.yaml.