View Deployment Details#
You can view deployment details including the deployment package name and version, whether deployment overrides are configured, the type of deployment (automatic or manual), the deployment status, and the deployment instance status.

Under Deployment Instance, use the search box to search for any Cluster ID, Cluster Name, or Status, or click the small up or down arrows next to the column names to sort the instances. For any deployment instance, you can view the following details:
Fields |
Description |
---|---|
Cluster ID |
Displays the cluster ID. This is a system-generated ID. Click the Cluster ID to view the deployment instance details, such as the running status of each application and the application resources being created. |
Cluster Name |
Displays the user given name of the cluster where the deployment is deployed. |
Status |
Displays the status of any given deployment instance with the status indicator, which presents an aggregated status for the instance. The available statuses include:
|
Applications |
Shows the number of applications in running status and the total number of applications in the deployment package. For example, the value 1/6 represents that of the total 6 applications in the deployment package, one application is in running status. |
Action |
Provides the option to view deployment instance details <view-deployment-instance-details> and View Cluster Details. Click the three dots icon (…) to perform the actions. |
View Deployment Instance Details#
The Deployment Instance page allows you to interact with the application resources that are deployed on a specific cluster. It provides the following information:
Deployment metadata.
Running status of each application.
Workloads and endpoints for each application.

Application Workloads#
A Workload is an application running on a cluster inside a set of containers. It can refer to either Virtual Machine or Pod where the application is Running. You can perform the following operations on the workloads:
For pod-type workloads, you can delete each pod or restart the pod.
For virtual machine-type workloads, you can start, stop, restart the VM, and also access the VM console. For more information see the Perform Actions on the Virtual Machines section.
Pod type workloads
The following figure shows us a deployed pod-type workload. This view shows detailed workload information including a name, created time, and status.

Fields |
Description |
---|---|
Type |
Displays the type of workload. In this case ‘Pod.’ |
Process ID |
Displays the Process ID (PID) of the pod, which is a unique identifier assigned to each running process in Kubernetes. |
Created |
Displays the date when the pod is created. |
Readiness |
Indicates the readiness of the pod. |
Status |
|
Action |
Allows you to delete the pod. |
VM type workloads
The following figure shows a deployed VM-type workload, which provides detailed workload information such as a name, created time, and status.

Fields |
Description |
---|---|
Type |
Displays the type of workload. In this case ‘Virtual Machine.’ |
Process ID |
Displays the Process ID (PID) of the virtual machine, which is a unique identifier assigned to each running process in Kubernetes. |
Created |
Displays the date when the virtual machine is created. |
Readiness |
Indicates the readiness of the virtual machine. |
Status |
|
Actions |
Allows you to start, stop, restart, and connect to the Console. For more information see the Perform Actions on the Virtual Machines section. |
Application Endpoints#
The Endpoint view shows all the services associated with the application.

Fields |
Description |
---|---|
Name |
Displays the name of the service. |
Hostname |
Displays the external domain name for the service. For more information, see EdgeDNS in the Load Balancer Package section. |
Ports |
Displays a list of service ports exposed. The port is hyperlinked if it is accessible through the Edge Orchestrator. For more information, see Service Link Support in Package an Application for the Registry section. |
Status |
Indicates the state of the service. |