> For the complete documentation index, see [llms.txt](https://docs.tensorwave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tensorwave.com/kubernetes/workloads.md).

# Workloads

The Workloads section of the Kubernetes tab gives you visibility into every workload resource running on your cluster. Use the left sidebar to navigate between resource types: Pods, Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs.

All views share a **Namespace** dropdown at the top of the page, which lets you filter results to a specific namespace. By default it is set to **All Namespaces**.

***

### Pods

A Pod is the smallest deployable unit in Kubernetes. Each Pod represents one or more containers running together on a node. The Pods view lists every Pod across your cluster.

<table><thead><tr><th width="179.8359375">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Pod Name</strong></td><td>The name of the Pod. Click the copy icon alongside it to copy the name to your clipboard.</td></tr><tr><td><strong>Namespace</strong></td><td>The namespace the Pod belongs to.</td></tr><tr><td><strong>Status</strong></td><td>The current lifecycle phase of the Pod. A green dot indicates the Pod is running normally.</td></tr><tr><td><strong>Node</strong></td><td>The node the Pod has been scheduled and is running on.</td></tr><tr><td><strong>Created</strong></td><td>The date and time the Pod was created, including timezone.</td></tr></tbody></table>

#### Pod Status Values

<table><thead><tr><th width="180.38671875">Status</th><th>Description</th></tr></thead><tbody><tr><td><strong>Running</strong></td><td>The Pod has been bound to a node and all containers have been started.</td></tr><tr><td><strong>Pending</strong></td><td>The Pod has been accepted by the cluster but is not yet running. It may be waiting for resources or for its container image to be pulled.</td></tr><tr><td><strong>Succeeded</strong></td><td>All containers in the Pod have completed successfully and will not be restarted.</td></tr><tr><td><strong>Failed</strong></td><td>One or more containers in the Pod terminated with an error.</td></tr><tr><td><strong>Unknown</strong></td><td>The state of the Pod could not be determined, usually due to a communication error with the node.</td></tr></tbody></table>

***

### Deployments

A Deployment manages a set of identical, stateless Pods and ensures the desired number of replicas are running at all times. If a Pod fails, the Deployment controller automatically replaces it.

<table><thead><tr><th width="179.8359375">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The name of the Deployment. Click the copy icon alongside it to copy the name to your clipboard.</td></tr><tr><td><strong>Namespace</strong></td><td>The namespace the Deployment belongs to.</td></tr><tr><td><strong>Ready</strong></td><td>The number of replicas currently ready out of the total desired, displayed as <code>ready/desired</code> (e.g. <code>1/1</code>).</td></tr><tr><td><strong>Available</strong></td><td>The number of replicas that are available to serve traffic.</td></tr><tr><td><strong>Updated</strong></td><td>The number of replicas that have been updated to the latest desired state.</td></tr><tr><td><strong>Created</strong></td><td>The date and time the Deployment was created, including timezone.</td></tr></tbody></table>

***

### StatefulSets

A StatefulSet manages Pods that require stable identities and persistent storage, such as databases. Unlike Deployments, each Pod in a StatefulSet has a unique, stable network identity and storage that persists across restarts.

<table><thead><tr><th width="179.52734375">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The name of the StatefulSet. Click the copy icon alongside it to copy the name to your clipboard.</td></tr><tr><td><strong>Namespace</strong></td><td>The namespace the StatefulSet belongs to.</td></tr><tr><td><strong>Ready</strong></td><td>The number of replicas currently ready out of the total desired, displayed as <code>ready/desired</code> (e.g. <code>3/3</code>). A value like <code>0/1</code> indicates replicas are desired but none are currently ready.</td></tr><tr><td><strong>Current</strong></td><td>The number of Pods that currently exist for this StatefulSet.</td></tr><tr><td><strong>Updated</strong></td><td>The number of Pods that have been updated to the latest version.</td></tr><tr><td><strong>Created</strong></td><td>The date and time the StatefulSet was created, including timezone.</td></tr></tbody></table>

***

### DaemonSets

A DaemonSet ensures that a copy of a specific Pod runs on every node in the cluster (or a subset of nodes). DaemonSets are commonly used for cluster-wide services such as log collectors, monitoring agents, and GPU device plugins.

<table><thead><tr><th width="180.1484375">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The name of the DaemonSet. Click the copy icon alongside it to copy the name to your clipboard.</td></tr><tr><td><strong>Namespace</strong></td><td>The namespace the DaemonSet belongs to.</td></tr><tr><td><strong>Desired</strong></td><td>The number of nodes that should be running the DaemonSet Pod.</td></tr><tr><td><strong>Current</strong></td><td>The number of nodes that are currently running the DaemonSet Pod.</td></tr><tr><td><strong>Ready</strong></td><td>The number of nodes running the Pod in a Ready state.</td></tr><tr><td><strong>Available</strong></td><td>The number of nodes where the Pod is available and able to serve its intended function.</td></tr><tr><td><strong>Created</strong></td><td>The date and time the DaemonSet was created, including timezone.</td></tr></tbody></table>

> **Note:** If the **Ready** or **Available** count is lower than **Desired**, it may indicate that some nodes are unable to run the Pod. This could be caused by resource constraints, node taints, or scheduling issues.

***

### Jobs

A Job creates one or more Pods to carry out a specific task and tracks whether those Pods complete successfully. Once all Pods finish, the Job is considered complete. Jobs are commonly used for one-off tasks such as installing modules or running database migrations.

<table><thead><tr><th width="180.31640625">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Job Name</strong></td><td>The name of the Job. Click the copy icon alongside it to copy the name to your clipboard.</td></tr><tr><td><strong>Job Status</strong></td><td>The current status of the Job. A green dot alongside <strong>Complete</strong> indicates the Job finished successfully.</td></tr><tr><td><strong>Namespace</strong></td><td>The namespace the Job belongs to.</td></tr><tr><td><strong>Kind</strong></td><td>The resource kind associated with the Job, where applicable.</td></tr><tr><td><strong>Created</strong></td><td>The date and time the Job was created, including timezone.</td></tr></tbody></table>

***

### CronJobs

A CronJob creates Jobs on a repeating schedule, similar to a cron task in Linux. CronJobs are useful for recurring automated tasks such as backups, report generation, or cleanup operations.

If no CronJobs have been configured on your cluster, the view will display **No Results Found**. This is expected for clusters that do not have any scheduled recurring workloads defined.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.tensorwave.com/kubernetes/workloads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.