DeployK8sApplication

The ID of the application. You can obtain the ID by calling the ListApplication operation. For more information, see ListApplication.

Run the script before stopping the job. For example, {"tcpSocket":{"host":"", "port":8080}}.

" "or {} indicates deletion. Do not set means ignore

Deployment environment variables, whose format must be JSON.

[{"name":"x","value":"y",{"name":"x2","value":"y2"}]. The key is fixed as name and value.

The minimum gap for batch release of pods. For more information, see minReadySeconds.

The commands run by the container.

Run the script in the format of {"exec":{"command":["cat","/etc/group"]}}. If this parameter is set to "" or {}, the service is deleted. If this parameter is not set, the service is ignored.

The container business status check fails. If the check fails, traffic that passes through the K8s service is not transferred to the container. Syntax: {"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 service is deleted. If this parameter is not set, the service is ignored.

Container viability status monitoring. Format:{"failureThreshold": 3,"initialDelaySeconds": 5,"successThreshold": 1,"timeoutSeconds": 1,"tcpSocket":{"host":"", "port":8080}}. If this parameter is set to "" or {}, the service is deleted. If this parameter is not set, the service is ignored.

Container startup Args command parameter, the format must conform to the JSON Array ["parameter 1","parameter 2"], where key is fixed as a string, empty must be set to an empty JSON Array "[]".

The number of application instances. Minimum value: 0.

The complete URL of the image, overwriting the Tag parameter of the image.

The CPU limit of application instances when the application is running. Unit: The number of cores. If it is set to 0, the number of cores is unlimited.

The memory limit of the application instance when the application is running. Unit: MB. If the value is set to 0, the quota is unlimited.

We recommend that you apply for the CPU quota for an application instance when the application is running.

Unit: The number of cores. If it is set to 0, the number of cores is unlimited.

We recommend that you apply for the memory quota for an application instance when the application is running. Unit: MB. The parameter value is set to 0, indicating that the certificate is not applied for.

The ID of the NAS file system to be mounted, which must be in the same region as the cluster. For a Mount target, a quota of available mount points is set, or its Mount point belongs to a vSwitch in the VPC. If you do not specify this parameter and the mountdess parameter is specified, the system automatically purchases a NAS file system and mounts the NAS file system to a vSwitch in the VPC.

The mount configuration description, which is a serialized JSON file. Example:[{"nasPath": "/k8s","mountPath": "/mnt",{"nasPath": "/files","mountPath": "/app/files"}]. nasPath indicates the path where files are stored. mountPath indicates the path where files are mounted in a container.

Currently only SSD is supported.

The configuration of mounting host files to the container where the application is running. Example:[{"type":"","nodePath":"/localfiles","mountPath":"/app/files" //,{"type":"Directory","nodePath":"/mnt","mountPath":"/app/storage"}]. Specifically, nodePath indicates the path of the host. mountPath indicates the path in the container. type indicates the mount type.

The address where the deployment package of the application is located. If you deploy an application through a FatJar or WAR package, you need to configure the deployment package address.

The version number of the deployment package. It is required for WAR and FatJar types. Please customize its meaning.

The JDK version on which the deployment package depends. Open JDK 7 and Open JDK 8 are supported. The error message returned because the specified image does not support this parameter.

The version of Tomcat that the deployment package is dependent on. This method is applicable to Spring Cloud and Dubbo applications deployed with a WAR package. The image does not support this parameter.

The version of the EDAS Container on which the deployment package depends. An HSF application deployed with a WAR package. Images do not support this parameter.

The URI encoding method. Valid values: ISO-8859-1, GBK, GB2312, and UTF-8.

Indicates whether the useBodyEncodingForURI is enabled.

Batch release policy

• Example 1: One phased-out machine + two subsequent batches + an automatic batch operation + a batch operation interval of 1 minute.{" type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":1},"grayUpdate":{"gray":1}}
• Example 2: one ASW + two subsequent batches + manual batches.{" type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"manual"},"grayUpdate":{"gray":1}}
• Example 3: This example is divided into two batches, an automatic batch, and a 0-minute interval.{" type":"BatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":0}}

Minimum CPU resource requirements. Unit: number of cores. Set the parameter to 0, indicating that no restriction is applied.

The maximum number of CPU cores that can be processed. Unit: cores. If the value is set to 0, no limit is applied.

Data volumes.

The ID of the deployment package version.

The description of the change record.

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

Indicates whether to distribute the application instances to multiple zones. " true: Yes. Other values: No.

The timeout period for publishing a single cloth. Unit: seconds.

Whether to connect to AHAS.

The Tomcat container configuration. Set the parameter to "" or "{}" to delete the configuration:

• useDefaultConfig: indicates whether to use custom configuration. A value of true indicates that the custom configuration is not used. A value of false indicates that the custom configuration is used. If you do not use the custom configuration, the following parameter settings will not take effect:
• contextInputType: Select the access path of the application.
  • war: The custom path is not required. The application access path is the WAR package name.
  • root: The custom path is not required. The application access path is /.
  • custom: enter a custom path in the custom path field.
• contextPath: The custom path. This parameter is required only when the contextInputType is of the custom type.
• httpPort: The Port range is 1024~65535. Ports smaller than 1024 need Root permissions to operate. Specify a port greater than 1024 because the container is configured with the Admin permission. If this parameter is not set, the default value 8080 is used.
• maxThreads: configures the number of connections to the connection pool. The default size is 400.

  Note This configuration has a great impact on the application performance. Please configure it by professionals.
• uriEncoding: the encoding format of a Tomcat API, including UTF-8, ISO-8859-1, GBK, and gb2312. If this parameter is not set, ISO-8859-1 is used by default.
• useBodyEncoding: whether to use BodyEncoding for URL.
• useAdvancedServerXml: choose whether to use advanced settings to customize the server.xml file. When the preceding parameter type and specific parameters do not meet your needs, you can select use advanced settings to edit the Server.xml file of Tomcat.
• serverXml: the content of the server.xml text file customized in advanced configurations. This parameter takes effect only when the useAdvancedServerXml is true.

Java startup parameters are used to configure startup parameters when a Java application is started. Configurable: correct configuration of memory, applications, GC policies, tools, service registration and discovery, and custom configurations. These configurations can reduce garbage collection (GC) overhead and improve server response time and throughput. The value of the startup parameter is a JSON-formatted string. The original parameter indicates the specified parameter value, and the system automatically uses all startup parameters as the Java startup parameters of the application. "" Or "{}" indicates that the configuration is deleted.

The Logstore configuration. Set the parameter to "" or "{}" to delete the configuration:

• Configs:
  • type: Collection type. Set the file type to file. Set the standard output type to stdout.
  • Logstore: the name of the logstore. Configure Logstore names in the same cluster as follows:
    • The Logstore name can only contain lowercase letters, digits, hyphens (-), and underscores (_).
    • The name must start and end with a lowercase letter or digit.
    • The project name must be 3 to 63 characters in length. If you do not set this parameter, the system will automatically generate the parameter.
  • LogDir: If the standard output type is set to stdout.log, the collection path is stdout.log. If the file type is set to file type, the file path is collected. You can specify wildcard characters. The collection path must be in the format of ^ /(. +) /(. *) ^/$.