turbot/kubernetes
steampipe plugin install kubernetes

Table: kubernetes_daemonset - Query Kubernetes DaemonSets using SQL

A Kubernetes DaemonSet ensures that all (or some) nodes run a copy of a pod. This is used to run system-level applications, such as log collectors, monitoring agents, and more. DaemonSets are crucial for maintaining the desired state and ensuring the smooth operation of Kubernetes clusters.

Some typical uses of a DaemonSet are:

  • running a cluster storage daemon on every node
  • running a logs collection daemon on every node
  • running a node monitoring daemon on every node

Table Usage Guide

The kubernetes_daemonset table provides insights into DaemonSets within Kubernetes. As a DevOps engineer, explore DaemonSet-specific details through this table, including the current status, spec details, and associated metadata. Utilize it to uncover information about DaemonSets, such as the number of desired and current scheduled pods, the DaemonSet's labels, and the node selector terms.

Examples

Basic Info

Explore which Kubernetes daemonsets are currently scheduled and ready, and determine how long they have been running. This information can be used to assess the status and performance of your Kubernetes environment.

select
name,
namespace,
desired_number_scheduled as desired,
current_number_scheduled as current,
number_ready as ready,
number_available as available,
selector,
age(current_timestamp, creation_timestamp)
from
kubernetes_daemonset;
select
name,
namespace,
desired_number_scheduled as desired,
current_number_scheduled as current,
number_ready as ready,
number_available as available,
selector,
strftime('%s', 'now') - strftime('%s', creation_timestamp) as age
from
kubernetes_daemonset;

Get container and image used in the daemonset

Explore the relationship between container names and images used within a daemonset. This can be helpful in understanding how resources are being utilized and managed across different namespaces.

select
name,
namespace,
c ->> 'name' as container_name,
c ->> 'image' as image
from
kubernetes_daemonset,
jsonb_array_elements(template -> 'spec' -> 'containers') as c
order by
namespace,
name;
select
name,
namespace,
json_extract(c.value, '$.name') as container_name,
json_extract(c.value, '$.image') as image
from
kubernetes_daemonset,
json_each(json_extract(template, '$.spec.containers')) as c
order by
namespace,
name;

Get update strategy for the daemonset

Analyze the update strategy settings for daemonsets to understand the maximum number of unavailable updates and their types. This is beneficial in managing and planning updates without disrupting the functioning of the system.

select
namespace,
name,
update_strategy -> 'maxUnavailable' as max_unavailable,
update_strategy -> 'type' as type
from
kubernetes_daemonset;
select
namespace,
name,
json_extract(update_strategy, '$.maxUnavailable') as max_unavailable,
json_extract(update_strategy, '$.type') as type
from
kubernetes_daemonset;

List manifest resources

Explore the status of various resources in your Kubernetes Daemonset to understand if resource allocation aligns with your current needs. This can help assess if resources are being efficiently utilized or if adjustments are needed.

select
name,
namespace,
desired_number_scheduled as desired,
current_number_scheduled as current,
number_available as available,
selector,
path
from
kubernetes_daemonset
where
path is not null;
select
name,
namespace,
desired_number_scheduled as desired,
current_number_scheduled as current,
number_available as available,
selector,
path
from
kubernetes_daemonset
where
path is not null;

Control examples

Schema for kubernetes_daemonset

NameTypeOperatorsDescription
_ctxjsonbSteampipe context in JSON form.
annotationsjsonbAnnotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata.
collision_countbigintCount of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.
conditionsjsonbRepresents the latest available observations of a DaemonSet's current state.
context_nametextKubectl config context name.
creation_timestamptimestamp with time zoneCreationTimestamp is a timestamp representing the server time when this object was created.
current_number_scheduledbigintThe number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod.
deletion_grace_period_secondsbigintNumber of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set.
deletion_timestamptimestamp with time zoneDeletionTimestamp is RFC 3339 date and time at which this resource will be deleted.
desired_number_scheduledbigintThe total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod).
end_linebigintThe path to the manifest file.
finalizersjsonbMust be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.
generate_nametextGenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided.
generationbigintA sequence number representing a specific generation of the desired state.
labelsjsonbMap of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services.
min_ready_secondsbigintThe minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0
nametextName of the object. Name must be unique within a namespace.
namespacetextNamespace defines the space within which each name must be unique.
number_availablebigintThe number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds).
number_misscheduledbigintThe number of nodes that are running the daemon pod, but are not supposed to run the daemon pod.
number_readybigintThe number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.
number_unavailablebigintThe number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds).
observed_generationbigintThe most recent generation observed by the daemon set controller.
owner_referencesjsonbList of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.
pathtextThe path to the manifest file.
resource_versiontextAn opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed.
revision_history_limitbigintThe number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.
selectorjsonbA label query over pods that are managed by the daemon set.
selector_querytextA query string representation of the selector.
source_typetextThe source of the resource. Possible values are: deployed and manifest. If the resource is fetched from the spec file the value will be manifest.
sp_connection_nametextSteampipe connection name.
sp_ctxjsonbSteampipe context in JSON form.
start_linebigintThe path to the manifest file.
tagsjsonbA map of tags for the resource. This includes both labels and annotations.
templatejsonbAn object that describes the pod that will be created.
titletextTitle of the resource.
uidtextUID is the unique in time and space value for this object.
update_strategyjsonbAn update strategy to replace existing DaemonSet pods with new pods.
updated_number_scheduledbigintThe total number of nodes that are running updated daemon pod.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- kubernetes

You can pass the configuration to the command with the --config argument:

steampipe_export_kubernetes --config '<your_config>' kubernetes_daemonset