Alauda Container Platform

Pod Parameters

The platform interface provides various information about the pods for quick reference. Below are some parameter explanations.

ParameterDescription
Resource Requests/LimitsThe effective resource (CPU, memory) requests and limits values for the pods. The calculation method for requests and limits values is the same; this document introduces using the limit values as an example, and the specific rules and algorithms are as follows:
  • When the pods only contains business containers (containers), the CPU/memory limit value is the sum of the CPU/memory limit values of all containers within the pods. For example: If the pods includes two business containers with CPU/memory limit values of 100m/100Mi and 50m/200Mi, the pods's CPU/memory limit value will be 150m/300Mi.
  • When the pods contains both init containers (initContainers) and business containers, the calculation steps for the pods's CPU/memory limit values are as follows:
    1. Take the maximum value of the CPU/memory limit values of all init containers.
    2. Take the sum of CPU/memory limit values of all business containers.
    3. Compare the results and take the maximum values of CPU and memory from both init containers and business containers as the pods's CPU/memory limit values.

    • Calculation Example: If the pods contains two init containers with CPU/memory limit values of 100m/200Mi and 200m/100Mi, the maximum CPU/memory limit value for the init containers would be 200m/200Mi. At the same time, if the pods also contains two business containers with CPU/memory limit values of 100m/100Mi and 50m/200Mi, the total limit value for the business containers will be 150m/300Mi. Therefore, the comprehensive CPU/memory limit value for the pods would be 200m/300Mi.
SourceThe computing component to which the pods belongs.
Restart CountThe number of restarts when the pods's status is abnormal.
NodeThe name of the node where the pods is located.
Service AccountThe Service Account is an account that allows processes and services in the Pod to access the Kubernetes APIServer, providing an identity for the processes and services. The Service Account field is visible only when the currently logged-in user has either the platform administrator role or the platform auditor role, and the YAML file of the Service Account can be viewed.