# daemonset

The describe daemonset command retrieves detailed information about a specific DaemonSet in the Kubernetes cluster. This includes metadata, pod scheduling, update strategy, rollout history, and associated pods running on each node.

## Usage

```
cldkctl describe daemonset [name] [flags]
```

## Steps

Follow the steps below to run and view the result of this command:

1. Run the following command in your terminal:

```
cldkctl describe daemonset [name] 
```

2. Replace `[name]` with the DaemonSet name you want to inspect.
3. To view the resource name, refer to the corresponding get daemonset section.
4. If the resource is located in a non-default namespace, include the `-n` or `--namespace` flag followed by the namespace name.

```
cldkctl describe [resource] [name] -n [namespace]
```

5. Once completed successfully, the detailed information about the specified DaemonSet will appear in your terminal. The output includes metadata, labels, container specifications, resource configurations, update strategy, and rollout status.

<figure><img src="/files/U2MvSHq3gvwrFlntuKOg" alt=""><figcaption></figcaption></figure>

The following table describes the additional fields specific to the DaemonSet resource.

| Column                                 | Describe                                                                             |
| -------------------------------------- | ------------------------------------------------------------------------------------ |
| spec.selector                          | Defines the label selector used to identify the pods managed by this DaemonSet.      |
| spec.template                          | Specifies the pod template that describes the pod configuration for each node.       |
| spec.template.spec.containers          | Lists the containers that run on each node as part of this DaemonSet.                |
| spec.template.spec.containers.name     | The name of the container.                                                           |
| spec.template.spec.containers.image    | The container image used by the DaemonSet.                                           |
| spec.template.spec.containers.ports    | The network ports exposed by the container.                                          |
| spec.template.spec.containers.resource | Specifies the CPU and memory limits and requests.                                    |
| spec.updateStrategy                    | Defines how updates are performed on the DaemonSet pods                              |
| spec.updateStrategy.type               | The update strategy type.                                                            |
| spec.updateStrategy.rollingUpdate      | Contains parameters controlling rolling update behavior.                             |
| status                                 | Displays the current scheduling and readiness status of DaemonSet pods across nodes. |
| status.currentNumberScheduled          | The number of pods currently scheduled by the DaemonSet.                             |
| status.desiredNumberScheduled          | The total number of nodes that should be running pods.                               |
| status.numberReady                     | The number of pods that are in the Ready state.                                      |
| status.numberUnavailable               | The number of pods that are not yet available or ready.                              |

## Flags

{% hint style="info" %}

1. This command supports [global flags](/guidance-for-individual/cloudeka-api-list/global-flags.md). Refer to the Global Flags section for details.
2. For common metadata fields, refer to the Common Output Fields table at the beginning of this section.
   {% endhint %}

| Flag       | Description                          |
| ---------- | ------------------------------------ |
| -h, --help | Help for describe daemonset command. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.ai/guidance-for-individual/cloudeka-api-list/command-reference/cldkctl-describe/daemonset.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.