Instances
Instances are individual containerized workloads running within clusters. In Kubernetes terminology, instances correspond to pods.
Overview
The Instances page provides visibility into all instances across your clusters. You can start, stop, restart, and monitor individual instances.
Instance Properties
| Property | Description |
|---|---|
| Instance ID | Unique identifier (mar-i-xxxx) |
| Cluster | Parent cluster where the instance runs |
| Status | Current state (running, degraded, restarting, stopped) |
| CPU | CPU utilization percentage |
| Memory | Memory utilization percentage |
| Restarts | Number of times the instance has restarted |
Instance Statuses
- Running - Instance is healthy and processing requests
- Degraded - Instance has issues but is still running
- Restarting - Instance is currently being restarted
- Stopped - Instance has been stopped
Managing Instances
Viewing Instance Details
Click the View button on any instance to see detailed information including resource usage and restart history.
Starting an Instance
To start a stopped instance:
- Click the Start button on the instance
- Monitor the operation in the operation queue
Stopping an Instance
To stop a running instance:
- Click the Stop button on the instance
- Confirm the action if prompted
- The instance status will change to “stopped”
Restarting an Instance
To restart an instance:
- Click the Restart button on the instance
- The instance will go through a restart process
- Status changes to “restarting” during the operation
Filtering
Use the search input to filter instances by:
- Instance ID
- Cluster name
- Status
Operation Queue
All instance operations are tracked, showing:
- Operation type (startInstance, stopInstance, restartInstance)
- Target instance ID
- Current status (pending, running, succeeded, failed)
Instance Health
Monitor the “Restarts” column to identify unstable instances. High restart counts may indicate:
- Application errors
- Resource constraints
- Configuration issues
- Health check failures
Last updated on