# Inspect an application

To view information about applications running in a cluster, from the menu select **Applications** then select the application you want to inspect.

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

The **Application details** screen is organized into four sections. The following tables explain all of the information to be found in each.

## Application tab

| Attribute        | Overview                                                                                                                             |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Name             | The name of the application.                                                                                                         |
| Stack            | The stack that the application belongs to (if any).                                                                                  |
| Namespace        | The namespace that the application is running in.                                                                                    |
| Application Type | The type of application (Pod, Deployment, StatefulSet, DaemonSet, etc).                                                              |
| Status           | Indicates whether or not the application is running. Where applicable, this also shows the replication state and number of replicas. |
| Creation         | Shows when the application was created and by whom, as well as how the application was deployed.                                     |
| Note             | Add a note about the application or edit an existing note.                                                                           |

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

## Placement tab

Here you'll find information about any placement constraints or preferences that have been defined for the application and how they're being applied.

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

## Events tab

Shows information about application-related events.

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

## YAML tab

This displays the YAML generated from the application deployment, and lets you edit the YAML for an application directly. Updates to your manifest made here are applied using the Kubernetes `patch` mechanism.

{% hint style="info" %}
Editing your YAML through this section is only available in Portainer Business Edition.
{% endhint %}

<figure><img src="/files/4Wj9ZnHU3Ck1Gj4SlnPn" alt=""><figcaption></figcaption></figure>

Make your edits then click **Apply changes** to update the deployment.

{% hint style="warning" %}
Editing the YAML is not available for resources in namespaces marked as system.
{% endhint %}

## Actions

Depending on how the application was deployed, a number of actions can be performed, including:

* [Editing the application](/sts/user/kubernetes/applications/edit.md)
* Edit the [Git settings](/sts/user/kubernetes/applications/manifest/create.md#repository)
* Pull and redeploy
* Perform a rolling restart of the application (Business Edition only).
* Redeploying the application (terminating all the services and recreating them).
* Rolling the application back to a previous configuration.
* Creating a [template](/sts/user/kubernetes/templates.md) from the application.

<figure><img src="/files/toQYIEKbKOWKmtOCCUV2" alt=""><figcaption><p>Some of the potential actions that may appear for your application</p></figcaption></figure>

### Configuration details

| Configuration                                | Overview                                                                                                                        |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Git deployment details                       | If your application was deployed from Git, you will see details about the Git deployment within the **Managed by Git** section. |
| Accessing the application                    | Shows which ports (if any) are published from the container.                                                                    |
| Auto-scaling                                 | Indicates the application's auto-scaling policy.                                                                                |
| Environment variables, ConfigMaps or Secrets | A list of any environment variables, ConfigMaps and secrets that have been defined for the application.                         |
| Data persistence                             | A list of the persistent folders and their details.                                                                             |

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

## Application pods

This section lists the pods running your application. Each pod displays the node it is running on (select to view node details), its IP address, the number of containers, and the creation date. You can restart or delete a pod using the buttons in the top-right corner of its tile. Note that restarting is only available if the connected cluster supports the `pods/restart` subresource.&#x20;

Select a pod to expand it and view its containers, including the image in use, the image pull policy, and the current status. From the **Actions** column, you can also access container stats, logs, and the console.

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


---

# Agent Instructions: 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.portainer.io/sts/user/kubernetes/applications/inspect.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.