> For the complete documentation index, see [llms.txt](https://doc.k8studio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.k8studio.io/documentation/deployment-view/overview.md).

# Overview

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

The Deployment View is a graphical representation of a cluster. It shows the different namespaces, subgroups within each namespace, ingress, services, workloads with their pods and statuses, as well as the Persistent Volume Claims. It also displays the links and relationships between each of these objects.

The Deployment View serves three main purposes:

1. To allow users to gain a deep understanding of what is running on the cluster in a matter of seconds.
2. Real-time monitoring of the objects. The Deployment View provides a real-time representation of the cluster and updates as the cluster data updates. This makes this view perfectly suited for reporting on objects' CRUD operations and, mostly, on the status of the different pods.
3. Low-code functionality. For beginners in Kubernetes, this view allows you to create objects and relationships visually with minimal code. So, if you are experimenting with Kubernetes or have a small organization with no professional DevOps, this view can help you take your first steps with a Kubernetes cluster.

In this section, we will describe the different graph objects and what they represent:

1. **Namespaces and Namespace Subgroups:** Namespaces are represented with rectangles that contain every other object available under the namespace. Namespaces also contain subgroups that are calculated using the `app.kubernetes.io/name` label of all the different objects that are part of the namespace. What K8studio does is calculate all the different subgroups and order the objects by subgroup. If this label is not set, the object will be part of the default subgroup. Namespaces are selectable, and they can be edited once selected using the sidebar.

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

2. **Workloads**: Any workload is color-coded in blue. The title section indicates the type of workload, the name of the workload, and the number of replicas when relevant. In the middle, there are icons that represent the containers that the pods of the workload are running. If the container is running a well-known image, K8Studio will use a custom icon; if not, a generic Kubernetes one is used. The bottom section shows the pods that are running, and they are color-coded by status.

<figure><img src="/files/5fGmd0geQTWnQuBypZac" alt=""><figcaption></figcaption></figure>

2. **Service**: Services and any network object are color-coded in green. The title and subtitle show the name and type of service. The central part displays the ports that the service is serving and the target port that the service is pointing to. If the port has been forwarded, a forward button will appear. This button is clickable and will navigate to the HTTP forwarded service.

<figure><img src="/files/86XHF3FX86iMjclqgBl5" alt=""><figcaption></figcaption></figure>

3. **Ingress:** The ingress object is color-coded in green, similar to other network objects. The tile contains the name of the ingress, and within the body, we can see the various paths and the ports they are pointing to.

<figure><img src="/files/3602WXlGgiMc1QcGWxDk" alt=""><figcaption></figcaption></figure>

3. **PVCs:** The Persistent Volumes Claim object and any store object are color-coded in purple. The Title will show the name of the PVC. The main bottom part shows 3 main things:
   * The accessModes
   * The capacity&#x20;
   * The status: Bound or Unbound

<figure><img src="/files/fcfgTJtfcdUajqsE34Y8" alt="" width="202"><figcaption></figcaption></figure>


---

# 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://doc.k8studio.io/documentation/deployment-view/overview.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.