When you use an elastic container instance to provide long-term services, you can use reserved instances to offset the cost of the elastic container instance. This topic describes how to use reserved instances.
Prerequisites
- Reserved instances are purchased based on your business requirements. For more information, see Purchase reserved instances.
- Reserved instances are checked and managed. For more information, see Split a reserved instance.
How to use reserved instances
A reserved instance is applicable only when you create an elastic container instance based on a specified Elastic Compute Service (ECS) instance type. For more information, see Create an ECI from a specified ECS instance type.
Add the following annotation
to the template
field of pod configurations. In this example, the reserved instance is used to purchase
an ecs.c5.large
instance.
annotations:
k8s.aliyun.com/eci-instance-type : "ecs.c5.large" # Replace the value with the actual ECS instance type in the following format: ecs.instance family.instance specification. For example, ecs.c6.3xlarge.
annotations
must be added to the spec
field of pod configurations. Specify the ECS instance type based on your requirements.
For more information about the supported ECS instance types, see Instance family.
Deployment example
annotations
must be added to the metadata
field of pod configurations.
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx
labels:
app: nginx
spec:
replicas: 2
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
annotations:
k8s.aliyun.com/eci-instance-type : "ecs.c5.large" # Replace the value with the actual ECS instance type based on your requirements.
containers:
- name: nginx
image: nginx:1.7.9
ports:
- containerPort: 80