DeployK8sApplication

The ID of the application to be deployed. You can query the ID by calling the ListApplication operation. For more information, see ListApplication.

The pre-stop script. An example of the value is {"tcpSocket":{"host":"", "port":8080}}.

If this parameter is set to "" or {}, the previous configuration is deleted. If this parameter is not specified, the previous configuration is still used.

The environment variables used to deploy the application. Set this parameter to a JavaScript object notation (JSON) array in the format of

[{"name":"x","value":"y"},{"name":"x2","value":"y2"}], where the keys are set to name and value.

The tag of the image.

The minimum time interval for the phased release of pods. For more information, see minReadySeconds.

The command used to start the container.

The post-start script. An example of the value is {"exec":{"command":["cat","/etc/group"]}}. If this parameter is set to "" or {}, the previous configuration is deleted. If this parameter is not specified, the previous configuration is still used.

The script used to check the service status of the container for the application. If the check fails, the traffic passing through the Kubernetes service is not transmitted to the container. Specify this parameter in the format of {"failureThreshold": 3,"initialDelaySeconds": 5,"successThreshold": 1,"timeoutSeconds": 1,"httpGet": {"path": "/consumer","port": 8080,"scheme": "HTTP","httpHeaders": [{"name": "test","value": "testvalue"}]}}. If this parameter is set to "" or {}, the previous configuration is deleted. If this parameter is not specified, the previous configuration is still used.

The script used to check the liveness of the container. Specify this parameter in the format of {"failureThreshold": 3,"initialDelaySeconds": 5,"successThreshold": 1,"timeoutSeconds": 1,"tcpSocket":{"host":"", "port":8080}}. If this parameter is set to "" or {}, the previous configuration is deleted. If this parameter is not specified, the previous configuration is still used.

The argument array in the container start-up command. Set this parameter to a JSON array in the format of ["args1","args2"], where each key is set to a string. If you want to cancel this configuration, set this parameter to an empty JSON array in the format of [].

The number of application instances. The minimum value is 0.

The absolute URL of the image. This parameter setting overwrites the setting of the ImageTag parameter.

The maximum number of CPU cores allowed for each application instance while the application is running. Unit: cores. To impose no limit, set this parameter to 0.

The maximum memory allowed for each application instance while the application is running. Unit: MB. To impose no limit, set this parameter to 0.

The CPU quota requested for each application instance while the application is running. We recommend that you configure this parameter.

Unit: cores. To impose no limit, set this parameter to 0.

The memory quota requested for each application instance while the application is running. We recommend that you configure this parameter. Unit: MB. To not apply for a memory quota, set this parameter to 0.

The ID of the Apsara File Storage NAS file system mounted to the container where the application is running. The NAS file system must be in the same region as the cluster. The NAS file system must have an available mount target or have a mount target on the vSwitch in the virtual private cloud (VPC) where the application is located. If this parameter is not specified and the mountDescs field exists, a NAS file system is automatically purchased and mounted to the vSwitch in the VPC by default.

The description of the NAS mounting configuration. Set this parameter to a serialized JSON string. For example, set this parameter to [{"nasPath": "/k8s","mountPath": "/mnt"},{"nasPath": "/files","mountPath": "/app/files"}]. The nasPath field specifies the file storage path, and the mountPath field specifies the path for mounting the file system to the container.

Only SSD disks are supported.

The configuration for mounting host files to the container where the application is running. For example, set this parameter to [{"type":"","nodePath":"/localfiles","mountPath":"/app/files"},{"type":"Directory","nodePath":"/mnt","mountPath":"/app/storage"}]. The nodePath field specifies the host path, the mountPath field specifies the path in the container, and the type field specifies the mount type.

The URL of the deployment package. This parameter is required if you use a FatJar or WAR package to deploy the application.

The version number of the deployment package. This parameter is required if you use a FatJar or WAR package to deploy the application. You must customize a version number.

The version of the Java Development Kit (JDK) on which the deployment package of the application depends. Open JDK 7 and Open JDK 8 are supported. This parameter is not supported if you use an image to deploy the application.

The version of the Tomcat container on which the deployment package of the application depends. This parameter is applicable to Spring Cloud and Apache Dubbo applications that are deployed by using WAR packages. This parameter is not supported if you use an image to deploy the application.

The version of EDAS Container on which the deployment package of the application depends. This parameter is applicable to High-speed Service Framework (HSF) applications that are deployed by using WAR packages. This parameter is not supported if you use an image to deploy the application.

The uniform resource identifier (URI) encoding scheme. Valid values: ISO-8859-1, GBK, GB2312, and UTF-8.

Specifies whether useBodyEncodingForURI is enabled.

The phased release policy.

• Example 1: 1 instance for canary release + 2 subsequent batches + automatic batching + 1-minute batch interval.{"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":1},"grayUpdate":{"gray":1}}
• Example 2: 1 instance for canary release + 2 subsequent batches + manual batching. {"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"manual"},"grayUpdate":{"gray":1}}
• Example 3: 2 batches + automatic batching + 0-minute batch interval. {"type":"BatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":0}}

The minimum number of CPU cores required. Unit: cores. To impose no limit, set this parameter to 0.

The maximum number of CPU cores allowed. Unit: cores. To impose no limit, set this parameter to 0.

The data volume.

The version ID of the deployment package.

The description of the change record.

The type of the container runtime. This parameter is applicable only to clusters that use sandboxed containers.

Specifies whether to distribute application instances to multiple zones. The value of true indicates yes and other values indicate no.

The timeout period for a single batch. Unit: seconds.

Specifies whether to enable access to Application High Availability Service (AHAS).

The Tomcat container configuration. If this parameter is set to "" or "{}", the previous configuration is deleted. Valid values:

• useDefaultConfig: specifies whether to use the custom configuration. The value of true indicates that the custom configuration is not used. The value of false indicates that the custom configuration is used. If the custom configuration is not used, the following parameters do not take effect.
• contextInputType: specifies whether to customize the access path for the application.
  • war: If you select this option, the application access path is the name of the WAR package. You do not need to specify a custom path.
  • root: If you select this option, the application access path is /. You do not need to specify a custom path.
  • custom: If you select this option, you must specify a custom path for the contextPath parameter.
• contextPath: specifies a custom path. This parameter is required only when the contextInputType parameter is set to custom.
• httpPort: specifies a port number. The port number ranges from 1024 to 65535. Though the admin permissions are configured for the container, the root permissions are required to perform operations on ports whose number is less than 1024. Therefore, enter a value greater than 1024 within the valid range. Default value: 8080.
• maxThreads: specifies the maximum number of connections in the connection pool. Default value: 400.

  Note This parameter greatly affects the application performance. We recommend that you set this parameter under professional guidance.
• uriEncoding: specifies the encoding format for Tomcat. Valid values: UTF-8, ISO-8859-1, GBK, and GB2312. Default value: ISO-8859-1.
• useBodyEncoding: specifies whether to use BodyEncoding for URL.
• useAdvancedServerXml: specifies whether to use advanced configurations to customize the server.xml file. If the preceding parameter types and specific parameters cannot meet your requirements, you can use advanced configurations to modify the server.xml file of Tomcat.
• serverXml: customizes the content of the server.xml file in advanced configurations. This parameter takes effect only when useAdvancedServerXml is set to true.

This parameter is used to configure Java startup parameters when a Java application is started. The Java startup parameters involve the memory, application, garbage collection (GC) policy, tools, service registration and discovery, and custom configurations. Proper parameter settings help reduce the GC overhead, shorten the server response time, and improve the throughput. Set this parameter to a JSON string. In the example, original specifies the configuration value and startup specifies a startup parameter. The system automatically concatenates all startup values as the configuration of the Java startup parameters for the application. If this parameter is set to "" or "{}", the previous configuration is deleted.

The Logstore configuration. If this parameter is set to "" or "{}", the previous configuration is deleted. Valid values:

• Configs:
  • type: the collection type. Set this parameter to file to specify the file type. Set this parameter to stdout to specify the standard output type.
  • Logstore: the name of the Logstore. Make sure that the name of the Logstore is unique in the cluster. The name must comply with the following rules:
    • The name can contain only lowercase letters, digits, hyphens (-), and underscores (_).
    • The name must start and end with a lowercase letter or a digit.
    • The name must be 3 to 63 characters in length. If this parameter is empty, the system automatically generates a name.
  • LogDir: If the standard output type is used, the collection path is stdout.log. If the file type is used, the collection path is the path of the collected file. Wildcards (*) are supported. The collection path must match the following regular expression: ^/(.+)/(.*)^/$.

Specifies whether to distribute application instances to multiple nodes. The value of true indicates yes and other values indicate no.

The traffic throttling policy for canary release.

The ID of the change process. You can query the ID by calling the GetChangeOrderInfo operation. For more information, see GetChangeOrderInfo.

The HTTP status code.

The additional information.

The ID of the request.