*1 Each pod is considered as 1 unit with 2vCPU / 4GB memory. If the size of a single pod exceeds this resource, the calculation will be done by using either the number of vCPUs rounded up by dividing it with 2vCPU or the memory size rounded up by dividing it with 4GB, whichever is greater.

​

** vCPU refers to a virtual CPU. For instance, if you're using Kubernetes, it corresponds to the CPU you configure in Kubernetes. In AWS, Microsoft Azure, and Google Cloud, this is denoted as vCPUs, while in Oracle Cloud Infrastructure (OCI), it is referred to as OCPUs. For the concept of vCPUs for each cloud provider, please refer to the following links:

​

• AWS

• Microsoft Azure

• Google Cloud

• Oracle Cloud Infrastructure

Consideration for contracted pod count during the contract period

The number of contracted pods is determined by calculating the count of maximum peak pods during the contract period, and this count is established for the duration of the contract. The product of the contracted pod count and the number of contracted months can be utilized within the range that doesn't surpass the cumulative maximum peak pod count for each month.

 

For example, if the pod allocation is as follows:
Jan: 1 pod; Feb: 1 pod; Mar: 3 pods; Apr: 4 pods; May: 4 pods; Jun: 5 pods; Jul: 3 pods; Aug: 3 pods; Sept: 3 pods; Oct: 3 pods; Nov: 3 pods; Dec: 3 pods. Total: 36 pods.
 

In this scenario, since the cumulative pod count is 36 pods, for a 1-year contract, 36 pods / 12 months = 3 pods/year (If a decimal point occurs, it is rounded up), resulting in 3 pods as the contracted pod count that you will receive.