Last updated：2021-04-14 15:43:53
You can explore KCE for free in a specific trial duration. For more information, see Service trial.
This topic describes how to try the KCE service for free.
KCE is a Platform as a Service (PaaS) service built on Infrastructure as a Service (IaaS) resources and services of Kingsoft Cloud. Before you try the KCE service, make sure that your account has been granted the permissions to try the services on which KCE depends.
|Kingsoft Cloud Elastic Compute (KEC)||Yes||N/A|
|Elastic IP (EIP)||Yes||N/A|
|Kingsoft Cloud File Storage (KFS)||No||This service is required for persistent storage.|
|Elastic Block Storage (EBS)||No||This service is required for persistent storage.|
|Elastic Physical Compute (EPC)||No||This service is required for testing a physical machine cluster.|
|Kingsoft Cloud Dedicated Host (KDH)||No||This service is required for testing a dedicated host cluster.|
You need to create host and network resources when you create a cluster. When you create these resources, select the
Pay-By-Daily-Config (Trial) billing mode.
You cannot centrally upgrade resources to formal editions in the KCE console. Instead, you need to perform related operations in corresponding consoles.
Some components of KCE, such as Cloud Provider and disk-provisioner, support only API calls. API calls are unavailable for trial services. Therefore, follow the instructions if you need to test the following features.
The disk-provisioner component is not supported during trial use. If you need to test container storage, log in to the KFS or EBS console and create an instance with the
Pay-By-Daily-Config (Trial) billing mode. Then, you can use volumes or static PVs to test container storage. For more information, see Use EBS volumes and Use KFS volumes.
Before you expose container services by using SLB, make sure that you have created corresponding instances with the
Pay-By-Daily-Config (Trial)billing mode in the EIP and SLB consoles and have bound the EIP to the SLB instance.
expose services by using an existing SLB instance in the following two ways:
For more information, see Access services by using SLB.
service.beta.kubernetes.io/ksc-loadbalancer-idannotation, and set the value to the ID of the existing SLB instance.
Auto scaling testing is not supported during trial use.
Did you find the above information helpful?
Please give us your feedback.
Thank you for your feedback.