Elastic Container Instance:Use the private pool of an elasticity assurance to create a pod

Feature description

Elasticity assurances allow you to obtain guaranteed access to resources for a period of one month to five years by paying only a small assurance fee. When you purchase an elasticity assurance, you must specify attributes, such as the region, the zone, and the ECS instance type. The system generates a private pool for the created elasticity assurance to reserve resources that match the attributes. For example, you can purchase an elasticity assurance to reserve resources of the ecs.c6.large instance type in Hangzhou Zone I. This way, you can access the reserved resources in the private pool during the guarantee period to create a pod of the ecs.c6.large instance type in Hangzhou Zone I. For more information, see Overview of Elasticity Assurance.

Billing rules

Elasticity assurances cannot be manually released. If you use an elasticity assurance, you are charged the following fees:

• A one-time assurance fee that is generated when you purchase the elasticity assurance.

• Hourly fees of the pod that is created by using the elasticity assurance.

  Important

  If you purchased applicable savings plans or regional reserved instances, you can apply them to the pod that is created by using the elasticity assurance. You cannot use zonal reserved instances to offset the bills of the pod.

Configuration description

During the guarantee period, you can use the reserved resources in the private pool of the elasticity assurance to create pods.

• Before you create a pod, make sure that the zones that are provided by the cluster vSwitch include the zone of the elasticity assurance. For information about how to specify zones, see Deploy pods in multiple zones.

• The private pool and ECS instance type that you specify when you create a pod must be the same as the private pool and ECS instance type that correspond to the purchased elasticity assurance. The following table describes the annotations that you can add when you use the private pool of an elasticity assurance to create a pod.

  Annotation	Example	Required	Description
  k8s.aliyun.com/eci-use-specs	ecs.c6.large	Yes	Specifies an ECS instance type. The ECS instance type must be the same as the ECS instance type that corresponds to the elasticity assurance. Note If you want to create pods based on special ECS instance types, such as GPU-accelerated ECS instance types or ECS instance types that use local disks, you must configure other relevant parameters. For more information, see Specify ECS instance types to create a pod.
  k8s.aliyun.com/eci-privatepool-matchcriteria	"Open"	Yes	Specifies the matching mode in which the system matches private pools. Valid values: Open: The system matches the instance with open private pools. Target: If you use this matching mode, you must specify a private pool ID. If you use targeted private pools to create pods, you must use this matching mode.
  k8s.aliyun.com/eci-privatepool-id	eap-2ze1g68k2melxkkl****	No	Specifies a private pool ID (the elasticity assurance ID). You can obtain the private pool ID on the Resource Reservations or Private Pools tab of the Resource Reservations page in the ECS console. If you set k8s.aliyun.com/eci-privatepool-matchcriteria to Target, you must configure this annotation. If you set k8s.aliyun.com/eci-privatepool-matchcriteria to Open, this annotation is invalid.

  Important

  • Annotations must be added to the metadata in the configuration file of the pod. For example, when you create a Deployment, you must add annotations in the spec.template.metadata section.

  • To use features of Elastic Container Instance, you can add annotations only when you create Elastic Container Instance-based pods. If you add or modify annotations when you update pods, these annotations do not take effect.

• After you create the pod, you can view the usage of the private pool of the elasticity assurance on the Resource Reservations or Private Pools tab of the Resource Reservations page in the ECS console.

  

  Note

  After a pod that is created by using an elasticity assurance is released, the capacity of the corresponding private pool is also released.

Configuration examples

• Example 1: If you do not specify an elasticity assurance ID, the system automatically matches open private pools.

  apiVersion: apps/v1
  kind: Deployment
  metadata:
    name: test
    labels:
      app: test
  spec:
    replicas: 1
    selector:
      matchLabels:
        app: nginx
    template:
      metadata:
        name: nginx-test
        labels:
          app: nginx
          alibabacloud.com/eci: "true" 
        annotations:
          k8s.aliyun.com/eci-use-specs: ecs.c6.large  # Specifies the ECS instance type that corresponds to the elasticity assurance.
          k8s.aliyun.com/eci-privatepool-matchcriteria: open  # Sets the matching mode in which the system matches private pools to open. The system automatically matches open private pools.
      spec:
        containers:
        - name: nginx
          image: registry.cn-shanghai.aliyuncs.com/eci_open/nginx:1.14.2
          ports:
          - containerPort: 80

• Example 2: If you use a targeted private pool to create a pod, you must specify an elasticity assurance ID.

  apiVersion: apps/v1
  kind: Deployment
  metadata:
    name: test
    labels:
      app: test
  spec:
    replicas: 1
    selector:
      matchLabels:
        app: nginx
    template:
      metadata:
        name: nginx-test
        labels:
          app: nginx
          alibabacloud.com/eci: "true" 
        annotations:
          k8s.aliyun.com/eci-use-specs: ecs.c6.large  # Specifies the ECS instance type that corresponds to the elasticity assurance.
          k8s.aliyun.com/eci-privatepool-matchcriteria: target  # Sets the matching mode in which the system matches private pools to target.
          k8s.aliyun.com/eci-privatepool-id: eap-2ze1g68k2melxkkl**** # Specifies a private pool ID (elasticity assurance ID).
      spec:
        containers:
        - name: nginx
          image: registry.cn-shanghai.aliyuncs.com/eci_open/nginx:1.14.2
          ports:
          - containerPort: 80