Skip to content

Manage containers

When an application encounters issues such as CrashLoopBack, slow startup, or sudden resource spikes, container-level inspection is often the most direct way to troubleshoot. The pod detail page in Control Hub aggregates information of all containers within a specific pod, providing events, visual charts, and logs to help you quickly identify and resolve problems.

View Pod details

To view the containers in a Pod:

  1. In the left navigation bar, click Browse, and select the target namespace from the first column.

  2. In the second column, expand Deployment, StatefulSet, or DaemonSet, then select the desired workload and drill down to its Pods list.

  3. Click on the target pod.

  4. In the third column, view the detailed pod information: containers

    SectionContent
    InfoBasic data such as pod status, restart count,
    IP, node, QoS, and images
    ContainersReal-time CPU/memory usage charts, image versions, status
    with options to export logs and access the container shell
    VolumesMounted persistent volumes, paths, and access modes
    Environment VariablesAll injected variables with expand-to-view support
    EventsRecent one-hour event logs for scheduling, probes, networking, etc.

    TIP

    You cannot directly edit pod YAML from this view. YAML configurations are managed by Olares via workload templates and webhooks.

View container status

For each container listed within a pod, you can:

  • Click the entry to view detailed container information, including status, image info, image pull policy, ports, and container metadata.
  • View container ports and environment variables.
  • Access the container’s command-line shell.
  • View or export container logs in real time.

container detail

Export container logs for troubleshooting

Exporting container logs, along with Events and resource charts, helps quickly identify issues such as CrashLoopBack, probe failures, or OOM (Out of Memory) errors.

Log operation

  1. In the left navigation bar, click Browse, and select the namespace for the problem application.
  2. In the second column, click to expand Deployments > Target deployment > Pods.
  3. In the Pods detail page, locate the abnormal container (typically marked with an orange status indicator), and click the article button.
  4. In the pop-up log window, you can: Log operation
    • Click download_2 to download the complete log file.
    • Click autorenew to refresh and view the latest log entries.
    • Click play_pause to start or pause real-time log updates.