Pods are the smallest deployable units in Kubernetes. A pod runs an instance of an independent application in Kubernetes. Each pod contains one or more containers that are tightly coupled. This topic describes how to view and change the configurations of pods and how to scale applications in the Alibaba Cloud Container Compute Service (ACS) console.
View pods
View pod details
Log on to the ACS console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side pane, choose .
On the Pods page, find the pod that you want to view and click View Details in the Actions column.
NoteOn the Pods page, you can modify and delete pods. For pods that are created by using a Deployment, we recommend that you use the Deployment to manage the pods.
The following table describes the status of a pod.
Status
Description
Initialized
All init containers are started.
Ready
The pod can serve requests and is added to the load balancing pools of all matching services.
ContainersReady
All containers in the pod are ready.
PodScheduled
The pod is scheduled to a node.
For more information, see Pod lifecycle.
Modify the upper limit and lower limit of CPU and memory resources for pods
After you create an application, you can modify the upper limit and lower limit of CPU and memory resources for the application pods. In this example, a Deployment is used.
Log on to the ACS console. In the left-side navigation pane, click Clusters.
On the Clusters page, click the name of a cluster. In the left-side navigation pane, choose Workloads > Pods.
On the Pds page, select a namespace from the Namespace drop-down list and click Edit in the Actions column.
On the editing page of the pod, specify the CPU and memory limits based on your business requirements. By default, the CPU or memory request is equal to the CPU or memory limit. Resources are billed on a pay-as-you-go basis. If you use a YAML template to set a resource limit that differs from the resource request, the resource request is automatically overridden to the value of the resource limit. For more information, see Resource specifications.