All Products
Search

This Product

    Container Service for Kubernetes:Manage pods

    Document Center

    Container Service for Kubernetes:Manage pods

    Last Updated:Mar 26, 2026

    Pods are the smallest deployable units in Kubernetes. Each pod runs an instance of an application, which can consist of one or more tightly coupled containers. This topic explains how to view, filter, diagnose, and modify pods, and how to scale pod replicas in the ACK console.

    On the Pods page, you can:

    • View pod details, logs, and status

    • Filter pods by name, label, IP address, or node

    • Diagnose pod issues

    • Edit a pod's YAML configuration

    • Modify CPU and memory resource limits

    • Scale the number of pod replicas

    Prerequisites

    Before you begin, ensure that you have:

    • A workload created in your cluster. For more information, see Workloads

    View pods

    View pod details

    1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

    2. On the Clusters page, click the name of the cluster you want to manage, then choose Workloads > Pods in the left-side navigation pane.

    3. On the Pods page, find the pod you want to inspect and click View Details in the Actions column.

    Note

    On the Pods page, you can modify and delete pods. For pods created by a Deployment, use the Deployment to manage them rather than editing the pods directly.

    The following table describes the pod status conditions shown in the console.

    Status Description
    Initialized All init containers are started.
    Ready The pod is able to serve requests and has been added to the load balancing pools of all matching services.
    ContainersReady All containers in the pod are ready.
    PodScheduled The pod has been scheduled to a node.

    For a full reference on pod phases and lifecycle, see Pod Lifecycle.

    View pod logs

    On the Pods page, find the pod whose logs you want to view, then click Logs in the Actions column.

    Filter pods

    On the Pods page, filter pods by name, label, pod IP address, or node IP address. You can also filter by the keys and values shown in the Label column.

    pod

    Diagnose a pod

    On the Pods page, find the pod you want to diagnose and click Diagnose in the Actions column. For more information, see Work with cluster diagnostics.

    Modify CPU and memory resource limits

    This procedure uses a Deployment as an example.

    1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

    2. On the Clusters page, click the name of the cluster you want to manage, then choose Workloads > Deployments in the left-side navigation pane.

    3. On the Deployments page, select a namespace from the Namespace drop-down list. Find the Deployment you want to update and click Edit in the Actions column.

    4. On the Edit page, set the Resource Limit and Required Resources parameters, then click Update.

    Important

    The maximum number of pods a cluster node supports depends on the network plug-in in use. For details, see the Compare Terway modes section of the "Work with Terway" topic.

    Edit a pod's YAML configuration

    1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

    2. On the Clusters page, click the name of the cluster you want to manage, then choose Workloads > Pods in the left-side navigation pane.

    3. On the Pods page, find the pod you want to edit and click Edit in the Actions column.

    4. In the Edit YAML dialog box, modify the configuration and click Update.

    Scale pods

    A Deployment manages pod replicas through a ReplicaSet. When you scale a Deployment, Kubernetes creates or removes pods to match the desired replica count, scheduling new pods on nodes with available resources.

    1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

    2. On the Clusters page, click the name of the cluster you want to manage, then choose Workloads > Deployments in the left-side navigation pane.

    3. Select the namespace where the Deployment is deployed, find the Deployment, then click Scale in the Actions column.

    4. In the Scale dialog box, set Desired Number of Pods to the target replica count (for example, 4) and click OK.

    Note

    Deployments use RollingUpdate as the default update strategy, which keeps a minimum number of pods available during the update. To adjust that minimum, edit the rolling update settings in the Deployment template.

    What's next