Workload Template Annotation Description

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

Note：

• If no security group is specified, a Pod is bound with the default security group in the same region by default. Ensure that the network policy of the default security group does not affect the Pod.
• To allocate GPU resources, you must specify eks.tke.cloud.tencent.com/gpu-type.
• Except eks.tke.cloud.tencent.com/gpu-type, the other four annotations related to resource allocation in the following table are optional. If you specify them, ensure that they are correct.
• 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, you must specify the cpu, mem, gpu-type, and gpu-count annotations and ensure that their values meet the GPU specifications in Resource Specifications.

Sample

The following example shows the complete GPU specifications of the security group bound to a Pod.

apiVersion: apps/v1
kind: StatefulSet
metadata:
  generation: 1
  labels:
    k8s-app: nginx
    qcloud-app: nginx
  name: nginx
  namespace: default
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: nginx
      qcloud-app: nginx
  strategy:
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 0
    type: RollingUpdate
  template:
    metadata:
      annotations:
        eks.tke.cloud.tencent.com/cpu: "2"
        eks.tke.cloud.tencent.com/gpu-count: "1"
        eks.tke.cloud.tencent.com/gpu-type: 1/4*V100
        eks.tke.cloud.tencent.com/mem: 10Gi
        eks.tke.cloud.tencent.com/security-group-id: "sg-dxxxxxx5,sg-zxxxxxxu"
        eks.tke.cloud.tencent.com/role-name: "cam-role-name"
        eks.tke.cloud.tencent.com/monitor-port: "9123"
        eks.tke.cloud.tencent.com/custom-metrics-url: "http://localhost:8080/metrics"
      creationTimestamp: null
      labels:
        k8s-app: nginx
        qcloud-app: nginx
    spec:
      containers:
      - image: nginx:latest
        imagePullPolicy: Always
        name: nginx
        resources:
          limits:
            cpu: "1"
            memory: 2Gi
            nvidia.com/gpu: "1"
          requests:
            cpu: "1"
            memory: 2Gi
            nvidia.com/gpu: "1"
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      imagePullSecrets:
      - name: qcloudregistrykey
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30

Virtual Node Annotation Description

EKS supports the virtual nodes. You can specify annotations in a YAML file to implement capabilities such as custom DNS, as shown below:

Sample

The example of a custom DNS configuration for a virtual node is as follows:

apiVersion: v1
kind: Node
metadata:
  annotations:
    eks.tke.cloud.tencent.com/resolv-conf:|
      nameserver 4.4.4.4
      nameserver 8.8.8.8

Service Annotation Description

EKS allows you to use existing CLBs to create services accessed through the public or private network. If you want to provide idle CLBs to created services or use the same CLB in a cluster, you can add annotations.

The elastic cluster also supports the same expansion protocol as the TKE cluster. For more information, see Service Extension Protocol.

Note：

• Ensure that your EKS does not share the same CLB with the CVM.
• When the existing CLBs are used:
  • Only CLBs created through the CLB console can be used. You cannot reuse CLBs automatically created by TKE.
  • Ports of Services that share the same existing CLB cannot be the same.
  • Cross-cluster Services cannot share the same CLB.

Sample

apiVersion: v1
kind: Service
metadata:
  annotations:
    service.kubernetes.io/tke-existed-lbid: lb-pxxxxxxq
    service.kubernetes.io/qcloud-share-existed-lb: true
  name: servicename
  namespace: default
spec:
  externalTrafficPolicy: Cluster
  ports:
  - name: tcp-80-80
    nodePort: 31728
    port: 80
    protocol: TCP
    targetPort: 80
  sessionAffinity: None
  type: LoadBalancer