tencent cloud

Billing Mode

For pods scheduled to the supernodes, there are two billing mode options, pay-as-you-go and spot billing. See Billing Overview, Product Pricing, and Purchase Limits.

Kubernetes Version

It supports clusters of v1.16 and above.

Default Quota

By default, up to 100 Pods can be scheduled to a supernode for each cluster. If the number of required Pods exceeds the quota limit, you can submit a ticket to apply for a higher quota. Tencent Cloud will assess your actual needs and increase your quota as appropriate.

Applying for a higher quota

1. Submit a ticket. On the Submit a ticket page, select the product name and issue type (Others), and then complete the ticket information.
2. In the Problem description field, enter a description such as "I want to apply for a higher quota for the Pod of cluster supernode." Then, enter the region where your cluster is located and your desired quota. Finally, enter your mobile number and other information as instructed.
3. Click to contact customer service.

Pod Configurations

Pod specification configuration

Pod specification configuration is the basis for billing the available resources and services when the container is running. For the resource specification configuration of supernode Pod and how to specify the resource specification, please see Resource Specifications and Specifying Resource Specifications.

Pod temporary storage

When each Pod scheduled to the supernode is created, a temporary image storage of no more than 20 GiB will be allocated.

Note：

• Temporary image storage will be deleted when the Pod lifecycle ends. Therefore, please do not store important data in it.
• The actual available storage will be less than 20 GiB due to the stored images.
• It is recommended to mount important data and large files to Volume for persistent storage.

Pod network

The Pods scheduled to supernode are on the same VPC network plane as the Tencent Cloud services such as CVM and TencentDB. Each Pod takes an IP address in the VPC subnet.

A Pod can connect to other Pods or Tencent Cloud services in the same VPC without any performance losses.

Pod isolation

The Pod scheduled to the supernode has the same security isolation as the CVM. Pods are scheduled and created on the underlying physical server of Tencent Cloud, and the resource isolation between Pods is guaranteed by virtualization technology during the creation.

Other special configurations

You can define template annotation in a YAML file to implement capabilities such as binding security groups, allocating resources and allocating EIP for Pods scheduled to the supernode. For more information about the configuration method, please see the following table:

Note：

• If no security group is specified, the Pod will be bound to the specified security group of the node pool by default. Please ensure that the network policy of the security group does not affect the normal operation of the Pod. For example, you need to open port 80 if the Pods provide service via port 80.
• To allocate CPU resources, you must specify both cpu and mem annotations and make sure that their values meet the CPU specifications in Resource Specifications. In addition, you can select Intel or AMD CPUs to allocate by specifying cpu-type. AMD CPUs are more cost-effective. For more information, see Product Pricing.
• To allocate GPU resources through the method specified in the annotation, you must specify the gpu-type and gpu-count annotations and ensure that their values meet the GPU specifications in Resource Specifications.

For samples, see Annotation.

Pod Limits

Workload limits

The Pods for DaemonSet workloads are not scheduled to the supernode.

Service limits

For cluster services using GlobalRouter Mode, if externaltrafficpolicy = local, the traffic is not forwarded to Pods scheduled to the supernode.

Volume limits

Pods that mount with hostpath volumes are not scheduled to the supernode.

Other limits

• The supernode feature is not available for the cluster without any server nodes.
• Pods that have enabled the Static IP Address cannot be scheduled to the supernode.
• Pods with hostPort specified are not scheduled to the supernode.
• Pods that with hostIP specified use the Pod IP as the hostIP by default.
• If Anti-affinity is enabled, only one pod is created on the supernode for the same workload.
• If the container logs are stored in the specified node file, and log collection is performed through the node file, the Pod logs on the supernode cannot be collected.