Configure free trial - Compute Nest - Alibaba Cloud Documentation Center

For private deployment services, service providers can offer a free trial that allows users to experience the service at no cost. Service providers can also create a trial service instance to test the service.

Introduction

The trial service provides most of the features of the official service, allowing users to experience the service for free. Service providers can enable the trial feature when creating or updating a private deployment service.
Once the services are configured and published, users can find them with free trial labels in the console's Service Catalog or My Services, and try these services.
During the creation of a trial service instance, all required cloud resources are created under Alibaba Cloud system accounts, and no fees are charged to users or service providers.

Important

Trial resources are deployed under the Alibaba Cloud system account. This feature is only for verifying whether cloud resources run successfully and applications can start properly (login supported in ECS/K8s scenarios). It does not support operations such as creating custom ECS images, viewing detailed cloud resource parameters (for example, OSS configuration), creating RAM users, or obtaining AccessKeys pair. To access more features, you must create and manage resources under your own personal or enterprise account.

Prerequisites

Only Compute Nest service providers can enable the trial feature.

Enable trial feature for a service

This section lists only the parameters that require special configuration for the trial feature. Other parameters should be filled in based on business requirements. For details about other parameters, see Create a private service, Update a service.

When creating a private service or editing a version and creating a new version, go to the Create Service or Modify Version page.
Click Add Parameter Set.
Change Trial Type to Trial Only.
It is recommended to select Instance Type (set and fix the ECS instance specifications) for package parameters. For non-package parameters, users can choose freely.
Click Create Service or Save Update, and click OK in the confirmation dialog box.
The Service Overview section will display the information such as the cost of the trial service.
In Basic Information, the Trial Status will change to Enabled.

Test the free trial service

Important

The trial service instance only applies to cloud resources created through Compute Nest. For cloud resources not created by Compute Nest, manually create pay-as-you-go resources for testing..

Create a trial service instance

After the service is created or updated, you can deploy a trial service instance using the following method.

Go to the Compute Nest - My Services page.
Find the service with trial enabled, and click the service card to enter the service details page.
In the Basic Details tab, click the Free Trial Deployment URL under Service Deployment to enter the deployment interface and create a trial service instance.
On Free Trial page, you can fill in the parameters as needed, and click Next: Confirm Order to complete the creation.

Connect to trial service instances to troubleshoot errors

If you encounter errors when testing a trial service instance, you can remotely connect to the service instance to view detailed error information or perform O&M operations.

You can go to the Compute Nest - Service Instance page, click Details in Action column of the service instance. In the Resources tab, find the corresponding ECS instance and click Remote Connection in the Actions column.

If the service provider needs to connect to a created Container Service for Kubernetes (ACK) cluster using kubectl, add specific code to the template to enable cluster access. After testing is complete, the relevant code should be removed from the template. Based on your current template content, modify the sample code according to the comments. Then, add the ClusterUserKubeconfig and ClusterApplicationJob resources to the Resources section of the template. The resource template code is as follows:

Warning

Please check carefully when deleting resource template code to avoid impacts on your business.

Resource Code Example and Usage for Deployed ACK Services

Resources:
  ClusterUserKubeconfig:
    Type: DATASOURCE::CS::ClusterUserKubeconfig
    DependsOn:
      - AckOrAcsClusterModule				  #Please modify this field according to the specific ACK resource name
    Properties:
      ClusterId:
        Fn::GetAtt:
          - AckOrAcsClusterModule			  #Please modify this field according to the specific ACK resource name
          - ClusterId
  ClusterApplicationJob:
    Type: ALIYUN::CS::ClusterApplication
    DependsOn:
      - ClusterUserKubeconfig
    Properties:
      YamlContent:
        Fn::Sub:
          - |
            apiVersion: batch/v1
            kind: Job
            metadata:
              name: kubectl
            spec:
              template:
                metadata:
                  name: kubectl
                spec:
                  restartPolicy: OnFailure
                  containers:
                  - name: intall
                    image: compute-nest-registry.cn-hangzhou.cr.aliyuncs.com/public/dtzar/helm-kubectl:3.12.0
                    command: [ "/bin/sh", "-c", "--" ] 
                    args:
                      - |
                        # Configure kubeconfig information
                        mkdir -p ~/.kube
                        echo '${KubeConfig}' | base64 -d >> ~/.kube/config
                        sleep 3

                        # Keep job running
                        while true
                           do sleep 300
                        done
          - KubeConfig:
              Fn::Replace:
                - "\n": ''
                - Fn::Base64Encode:
                    Fn::GetAtt:
                      - ClusterUserKubeconfig
                      - Config
      ClusterId:
        Fn::GetAtt:
          - AckOrAcsClusterModule			#Please modify this field according to the specific ACK resource name
          - ClusterId
      DefaultNamespace:
        Ref: 'ALIYUN::StackName'

After the resources are created, you can go to the Compute Nest - Service Instance page, and perform the following operations in the Resources tab of the service instance details page:

Find the Pod Container Resource named kubectl, and click Remote Connection.

Enter the Pod and use kubectl commands for debugging.