K8s
Create an EDAS k8s application.For information about EDAS K8s Application and how to use it, see What is EDAS K8s Application.
NOTE: Available since v1.105.0.
Import
EDAS k8s application can be imported as below, e.g.
$ pulumi import alicloud:edas/k8sApplication:K8sApplication new_k8s_application application_idConstructors
Properties
The description of the application
The name of the application you want to create. Must start with character,supports numbers, letters and dashes (-), supports up to 36 characters
Used in combination with the command, the parameter of the command is a JsonArray string in the format: [{"argument":"-c"},{"argument":"test"}]. Among them, -c and test are two parameters that need to be set.
EDAS-Container version that the deployed package depends on. Image does not support this parameter.
Deployment environment variables, the format must conform to the JSON object array, such as: {"name":"x","value":"y"},{"name":"x2","value":"y2"}, If you want to cancel the configuration, you need to set an empty JSON array "" to indicate no configuration.
Public network SLB ID. If not configured, EDAS will automatically purchase a new SLB for the user. It has been deprecated, and new resource 'alicloud_edas_k8s_slb_attachment' replaces it.
The public network SLB front-end port, range 1~65535. It has been deprecated and new resource 'alicloud_edas_k8s_slb_attachment' replaces it.
The public network SLB protocol supports TCP, HTTP and HTTPS protocols. It has been deprecated, and new resource 'alicloud_edas_k8s_slb_attachment' replaces it.
The private SLB back-end port, is also the service port of the application, ranging from 1 to 65535. It has been deprecated, and new resource 'alicloud_edas_k8s_slb_attachment' replaces it.
The configuration of the host file mounted to the container. For example: [{"type":"","nodePath":"/localfiles","mountPath":"/app/files"},{"type":"Directory","nodePath":"/mnt", "mountPath":"/app/storage"}]. Among them, nodePath is the host path; mountPath is the path in the container; type is the mount type.
The ID corresponding to the EDAS namespace, the non-default namespace must be filled in.
Mount configuration description, as a serialized JSON. For example: [{"nasPath": "/k8s","mountPath": "/mnt"},{"nasPath": "/files","mountPath": "/app/files"}]. Among them, nasPath refers to the file storage path; mountPath refers to the path mounted in the container.
The ID of the mounted NAS must be in the same region as the cluster. It must have an available mount point creation quota, or its mount point must be on a switch in the VPC. If it is not filled in and the mountDescs field exists, a NAS will be automatically purchased and mounted on the switch in the VPC by default.
Application package type. Optional parameter values include: FatJar, WAR and Image.
The url of the package to deploy.Applications deployed through FatJar or WAR packages need to configure it.
The version number of the deployment package. WAR and FatJar types are required. Please customize its meaning.
Container service status check. If the check fails, the traffic passing through K8s Service will not be transferred to the container. The format is: {"failureThreshold": 3,"initialDelaySeconds": 5,"successThreshold": 1,"timeoutSeconds": 1, "httpGet": {"path": "/consumer","port": 8080,"scheme": "HTTP","httpHeaders": [{"name": "test","value": "testvalue"} ]}}.
When the application is created, the CPU quota of the application instance, unit: number of millcores, similar to request_cpu
When the application is created, the memory limit of the application instance, unit: M. When set to 0, it means unlimited.
The Tomcat version that the deployment package depends on. Applicable to Spring Cloud and Dubbo applications deployed through WAR packages. Image does not support this parameter.