CPU (Cores) | Memory Range (GiB) | Granularity of Memory Range (GiB) |
0.25 | 0.5, 1, 2 | - |
0.5 | 1, 2, 3, 4 | - |
1 | 1 - 8 | 1 |
2 | 4 - 16 | 1 |
4 | 8 - 32 | 1 |
8 | 16 - 32 | 1 |
12 | 24 - 48 | 1 |
16 | 32 - 64 | 1 |
template annotation
in a YAML file to implement capabilities such as binding security groups, allocating resources, and allocating EIPs for Pods scheduled to super nodes. For configuration details, see the following table:cpu
and mem
annotations in line with the CPU specifications in Resource Specifications.gpu-type
and gpu-count
annotations and ensure that their values meet the GPU specifications in Resource Specifications.Annotation Key | Annotation Value and Description | Required |
eks.tke.cloud.tencent.com/security-group-id | Default security group bound to a workload. Security group ID: You can enter multiple IDs and separate them by comma, for example, sg-id1,sg-id2 . Network policies take effect based on the sequence of security groups. | No. If you don't specify it, the security group specified by the node pool is bound by default. If you specify it, make sure that the security group ID already exists in the same region. |
eks.tke.cloud.tencent.com/cpu | Number of CPU cores required by a Pod. For more information, see Resource Specifications. The unit is cores by default and doesn't need to be specified. | No. If you specify it, make sure that the specification is supported, and you need to enter the cpu and mem parameters. |
eks.tke.cloud.tencent.com/mem | Amount of memory required by a Pod. For more information, see Resource Specifications. You need to specify the unit, for example, 512 MiB, 0.5 GiB, or 1 GiB. | No. If you specify it, make sure that the specification is supported, and you need to enter the cpu and mem parameters. |
eks.tke.cloud.tencent.com/cpu-type | CPU model required by a Pod. Currently, Intel and AMD are supported. For more information on configurations supported by S4, S3, and other models, see Resource Specifications. | No. If you don't specify it, the system will match the most suitable specification according to Specifying resource specifications. If the matched specification is supported by both Intel and AMD, the Intel specification is preferred. |
eks.tke.cloud.tencent.com/gpu-type | GPU model required by a Pod. Currently, V1001/4T41/2T4T4 are supported. You can specify the model by priority, for example, "T4,V100" indicates T4 Pods will be created first. If the T4 resources in the selected region are insufficient, V100 Pods will be created. For more information on configurations, see Resource Specifications. | It is required if you need a GPU. When specifying it, make sure that the GPU model is supported; otherwise, an error will be reported. |
eks.tke.cloud.tencent.com/gpu-count | Number of GPUs required by a Pod. For more information, see Resource Specifications. The unit is cards by default and doesn't need to be specified. | No. If you specify it, make sure that the specification is supported. |
eks.tke.cloud.tencent.com/retain-ip | Static IP of a Pod. Enter the value of "true" to enable this feature. If a Pod with the static IP enabled is terminated, its IP will be retained for 24 hours by default. If the Pod is rebuilt within 24 hours, its IP can still be used; otherwise, its IP may be occupied by other Pods. It is valid only for StatefulSet and raw Pods. | No |
eks.tke.cloud.tencent.com/retain-ip-hours | Modifies the default retention period of a Pod's static IP. Enter a number. The unit is hours, and the default value is 24 hours. An IP can be retained for up to one year. It is valid only for StatefulSet and raw Pods. | No |
eks.tke.cloud.tencent.com/eip-attributes | Indicates that the Pod of the workload needs to be associated with an EIP. When the value is "", the default EIP configuration is used. You can enter the cloud API parameter json of the EIP in "" to customize the configuration. For example, if the value of annotation is '{"InternetMaxBandwidthOut":2}', the bandwidth is 2 Mbps. Note that this cannot be used for non-bill-by-IP accounts. | No |
eks.tke.cloud.tencent.com/eip-claim-delete-policy | Indicates whether to repossess the EIP after the Pod is deleted. Never indicates not to repossess. The default value is to repossess. This parameter takes effect only when eks.tke.cloud.tencent.com/eip-attributes is specified. Note that this cannot be used for non-bill-by-IP accounts. | No |
eks.tke.cloud.tencent.com/eip-id-list | If the workload is a StatefulSet, you can also specify one or multiple existing EIPs, such as "eip-xx1,eip-xx2". Note that the number of StatefulSet Pods must be less than or equal to the number of EIP IDs specified in this annotation; otherwise, Pods that cannot be allocated with EIPs will be in the "Pending" status. Note that this cannot be used for non-bill-by-IP accounts. | No |
cloud.tencent.com/qcloud-cbs
types are supported (CFS not supported).gpu-type
field in the annotation; otherwise, scheduling to super nodes is not supported. Different GPU Pod types come with different CPU and memory specifications, which don't need to be specified. If you need to specify them, make sure that they are identical to those supported by the GPU; otherwise, scheduling will fail.tke-eni-ip-webhook
namespace cannot be scheduled to super nodes.
Was this page helpful?