Workload View

In Kubernetes, a Pod is the smallest and most basic deployable object. It represents a single instance of a running process in your cluster and can host one or more tightly coupled containers that share the same network namespace and storage volumes. Pods are often ephemeral and are typically not created directly by users but managed through higher-level controllers like Deployments, StatefulSets, or Jobs. Each Pod runs on a Node and includes specifications for its containers, such as images, environment variables, and health checks.
Learn more about Pods in the official Kubernetes documentation 

The Pods table displays all running Pods in the cluster. You can click on any Pod to open a details panel with in-depth information, including Overview, Details, YAML editing, and Events. Use the Namespace drop-down to filter Pods by namespace, or the Search Resources field to quickly locate a specific Pod.

Each column supports sorting in ascending or descending order. You can also select multiple Pods using the checkboxes, and then use the Delete Selected button to remove them in bulk. The Refresh button reloads the table to show the latest state. Additional actions like Edit and Delete are available via the More Actions menu on each row. 

Default Columns:

• Name: Pod name

• Namespace: Pod’s namespace

• Containers: Number of containers in the pod

• Restarts: Restart count

• Controlled By: Controller managing the pod

• Node: Hosting node

• QoS: Quality of Service class

• Age / Status: Uptime and current state

• Options: View Logs, Edit, Delete

In Kubernetes, a Deployment is a higher-level controller that manages the lifecycle of Pods and Replica Sets. It provides declarative updates for your applications and ensures that the desired number of Pod replicas are running and available at all times. Deployments handle rolling updates, rollbacks, and scaling seamlessly, making them the standard way to manage stateless applications in Kubernetes. They simplify operations by automating pod creation, health monitoring, and replacement of failed Pods.
Learn more about Deployments in the official Kubernetes documentation

The Deployments table displays all active Deployments in the cluster. You can click on any Deployment to open a details panel with sections like Overview, Details, YAML, and Events. Use the Namespace drop-down to filter Deployments by namespace, or the Search Resources field to quickly find a specific Deployment.

Each column supports sorting in ascending or descending order. You can select multiple Deployments using the checkboxes, then use the Delete Selected button to remove them in bulk. The Refresh button reloads the data to reflect the latest state. Additional actions like Edit and Delete are available through the More Actions menu on each row.

Default Columns:

• Name: Deployment name

• Namespace: Associated namespace

• Available Pods: Running pod count

• Replicas: Current / desired replicas

• Age / Status: Deployment status and uptime

• Conditions: 

• Options: Scale, Edit, View YAML, Delete

In Kubernetes, a Daemon Set ensures that a specific Pod runs on every node in the cluster (or a targeted subset). This is ideal for deploying background agents like log collectors, monitoring tools, or network daemons that must run on all nodes. When new nodes are added to the cluster, the Daemon Set automatically adds the Pod to them, ensuring consistent cluster-wide coverage.

Learn more about Daemon Sets in the official Kubernetes documentation

The Daemon Sets table lists all active Daemon Sets in the cluster. Clicking on a Daemon Set opens a details panel with tabs like Overview, Details, YAML, and Events. You can filter the table by namespace using the Namespace drop-down, or use the Search Resources field to find a specific DaemonSet.

You can sort each column, select multiple Daemon Sets using checkboxes, and delete them in bulk via the Delete Selected button. Use the Refresh button to reload the table with current cluster data. Additional actions like Edit and Delete are accessible through the More Actions menu.

Default Columns:

• Name: Daemon Set name

• Namespace: Associated namespace

• Pods: Running / desired pods

• Node Selector: Target nodes (if defined)

• Age / Status: Rollout status and uptime

• Options: Edit, Delete

In Kubernetes, a Stateful Set is used to manage stateful applications that require stable network identities and persistent storage. Unlike Deployments, Stateful Sets assign a unique identity to each Pod and maintain the order of deployment, scaling, and termination. This makes them suitable for databases, distributed systems, and clustered services.

Learn more about Stateful Sets in the official Kubernetes documentation

The Stateful Sets table lists all Stateful Sets across the cluster. Clicking a Stateful Set reveals a details panel with tabs including Overview, Details, YAML, and Events. Use the Namespace drop-down to filter by namespace or search with the Search Resources input.

You can sort columns, select multiple Stateful Sets with checkboxes, and use the Delete Selected button for bulk deletion. The Refresh button reloads the view. Additional actions like Edit and Delete are available under the More Actions menu.

Table Summary:
Lists Stateful Sets with pod ordering and volume tracking.

Default Columns:

• Name: Stateful Set name

• Namespace: Target namespace

• Replicas: Current / desired replica count

• Age / Status: Uptime and state

• Options: Edit, Delete

In Kubernetes, a Replica Set is a controller that ensures a specified number of identical Pods are running at all times. It's mostly used by Deployments to handle pod replication, but can also be used independently. Replica Sets automatically replace failed Pods and balance load across available nodes.

Learn more about Replica Sets in the official Kubernetes documentation

The Replica Sets table displays all active Replica Sets in the cluster. You can open a details panel by clicking any entry, with tabs like Overview, Details, YAML, and Events. Use the Namespace drop-down to narrow the list, or the Search Resources field for quick access.

Sort columns as needed, select multiple Replica Sets using checkboxes, and delete them with the Delete Selected button. Use Refresh to update the view. You can also Edit or Delete a Replica Set using the More Actions menu.

Default Columns:

• Name: Replica Set name

• Namespace: Namespace in which it's running

• Pods: Ready / desired pod count

• Age / Status: Active time and state

• Options: View YAML, Delete

In Kubernetes, a Replication Controller is a legacy controller used to maintain a stable number of Pods running at any given time. While largely replaced by Replica Sets and Deployments, it is still supported and used in older configurations or simpler setups.

Learn more about Replication Controllers in the official Kubernetes documentation

The Replication Controllers table shows all such resources in the cluster. Selecting a Replication Controller opens a details panel with sections like Overview, Details, YAML, and Events. Use the Namespace drop-down and Search Resources input to filter or locate items.

You can sort columns, select multiple items using checkboxes, and delete them in bulk with the Delete Selected button. Use Refresh to update the list. Additional actions like Edit and Delete are found under the More Actions menu.

Default Columns:

• Name: Replication Controller name

• Namespace: Namespace in which it runs

• Replicas: Current / desired replicas

• Selector: Label selector used to manage pods

• Options: Edit, Delete

In Kubernetes, a Cron Job creates Jobs on a scheduled basis, similar to Unix cron. It's ideal for periodic tasks like backups, log rotation, or clean-up routines. Cron Jobs define a time-based schedule and manage Job creation automatically.

Learn more about Cron Jobs in the official Kubernetes documentation

The Replica Sets table displays all active Cron Jobs in the cluster. You can open a details panel by clicking any entry, with tabs like Overview, Details, YAML, and Events. Use the Namespace drop-down to narrow the list, or the Search Resources field for quick access.

Sort columns as needed, select multiple Cron Jobs using checkboxes, and delete them with the Delete Selected button. Use Refresh to update the view. You can also Edit or Delete a Cron Jobs using the More Actions menu.

Default Columns:

• Name: Cron Job name

• Namespace: Namespace for the job

• Schedule: Cron expression (e.g., */5 * * * *)

• Active Jobs: Currently running instances

• Last Schedule: Time of last job trigger

• Age : Age and last execution status

• Options:  Edit, Delete

In Kubernetes, a Job is used to run short-lived or batch tasks that need to complete successfully one or more times. Jobs ensure that a specified number of Pods run to completion and handle retrying on failure. They are ideal for data processing, database migrations, and scheduled tasks.

Learn more about Jobs in the official Kubernetes documentation

The Jobs table displays all active jobs in the cluster. You can open a details panel by clicking any entry, with tabs like Overview, Details, YAML, and Events. Use the Namespace drop-down to narrow the list, or the Search Resources field for quick access.

Sort columns as needed, select multiple jobs using checkboxes, and delete them with the Delete Selected button. Use Refresh to update the view. You can also Edit or Delete a Jobs using the More Actions menu.

Default Columns:

• Name: Job name

• Namespace: Namespace where it's scheduled

• Completions: Successful / desired completions

• Age / Status: Time since started, completion state

• Options: View logs, Delete