Elastic cluster is a service of Elastic Kubernetes Service (EKS). Before you use this service, please read the following information.
EKS adopts the pay-as-you-go billing method. For more information about the bills, please see Billing Overview, Product Pricing, and Purchase Limits.
Container runtime resources and bills depend on the pod specification configuration. Please note the pod specification configuration and specific methods supported by elastic clusters. For more information, please see Resource Specifications and Specifying Resource Specifications.
Upon the creation of each pod, temporary image storage less than 20 GiB is allocated.
Note:
- Temporary image storage will be deleted when the pod lifecycle ends. Therefore, ensure that important data is not stored in it.
- Due to image storage, the actual available storage is less than 20 GiB.
- You are recommended to mount important data and large files to Volume for persistent storage.
Kubernetes versions earlier than 1.12 are not supported.
Elastic clusters do not have nodes. Therefore, some dependent node components, such as Kubelet and Kube-proxy, are not supported.
Currently, adding or managing a physical node is not supported.
Only kernel parameters started with "net" can be defined.
You cannot deploy workloads of the DaemonSet type through EKS.
You cannot deploy services of the NodePort type through EKS.
You cannot use Linux filesystem events with inotify, which is a feature of emptyDir volumes.
Was this page helpful?