Elastic Container Instance:Create a pod using a private resource pool with elasticity assurance

Overview

With elasticity assurance, you pay a low upfront fee to guarantee resource availability for a fixed term ranging from 1 month to 5 years. When purchasing elasticity assurance, specify properties such as region, zone, and instance type. The system reserves matching resources in a private pool. For example, if you reserve ecs.c6.large instances in Zone I of China (Hangzhou), you can create ECI instances of that exact specification in the same zone at any time during the assurance period. For more information, see Elasticity assurance.

Billing details

You cannot manually release elasticity assurance after purchase. During its use, you incur the following charges:

• Pay a one-time assurance fee when purchasing elasticity assurance.

• After successfully creating an ECI instance from the associated private resource pool, pay the hourly bill for the ECI instance.

  Important

  ECI instances created from a private resource pool linked to elasticity assurance can still apply existing savings plans and regional reserved instances to reduce billing costs, but they cannot use zonal reserved instances.

Configuration details

During the assurance period, use the associated private resource pool to create ECI instances.

• Before creation, confirm that the vSwitch configured for your cluster maps to a zone covered by your elasticity assurance. For guidance on configuring zones, see Create pods across multiple zones.

• At creation time, the specified private pool and ECS instance type must match your purchased elasticity assurance. Use the following annotations:

  Annotation	Example value	Required	Description
  k8s.aliyun.com/eci-use-specs	ecs.c6.large	Yes	Specify the ECS instance type. It must match the instance type in your elasticity assurance. Note For special instance types such as GPU or local disk instances, configure additional parameters. For details, see Create a pod with a specified ECS instance type.
  k8s.aliyun.com/eci-privatepool-matchcriteria	"Open"	Yes	Set the private pool matching mode. Valid values: Open: The system automatically matches an available open private pool. Target: You must also specify a private pool ID. Use this mode if your private pool is dedicated. Important In Open mode, if the private pool lacks capacity, the system fills the gap using public pool resources. In Target mode, insufficient private pool capacity causes ECI instance creation to fail. In Open mode, ECI cannot match private pools with tags. Remove any tags from your private pool before using Open mode, or matching will fail.
  k8s.aliyun.com/eci-privatepool-id	eap-2ze1g68k2melxkkl****	No	Specify the private pool ID (which is the elasticity assurance ID). Find it on the Resource reservation page in the ECS console under the Resource Reservations or Private Pools tab. If k8s.aliyun.com/eci-privatepool-matchcriteria is set to Target, you must include this annotation. If k8s.aliyun.com/eci-privatepool-matchcriteria is set to Open, this annotation has no effect.

  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.

  • Elastic Container Instance-related annotations are only applied when a pod is created. Adding or modifying these annotations on an existing pod will have no effect.

• After creation, check usage of your private resource pool on the Resource reservation page in the ECS console under the Resource Reservations or Private Pools tab.

  The Instances column shows usage in the format "used/total". For example, 0/1 means 0 of 1 instances are used, and 1/1 means all 1 instance is used.

  Note

  When you release an ECI pod that uses elasticity assurance, the corresponding private pool capacity is released immediately.

Configuration examples

• Example 1: Do not specify an elasticity assurance ID. The system automatically matches an open private pool.

  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  # Specify the ECS instance type covered by elasticity assurance
          k8s.aliyun.com/eci-privatepool-matchcriteria: open  # Use open mode to let the system auto-match an open private pool
      spec:
        containers:
        - name: nginx
          image: registry.cn-shanghai.aliyuncs.com/eci_open/nginx:1.14.2
          ports:
          - containerPort: 80

• Example 2: The private pool linked to elasticity assurance is dedicated. You must specify the 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  # Specify the ECS instance type covered by elasticity assurance
          k8s.aliyun.com/eci-privatepool-matchcriteria: target  # Use target mode
          k8s.aliyun.com/eci-privatepool-id: eap-2ze1g68k2melxkkl**** # Specify the 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