Delete an application that you do not need to use any longer. Applications cannot be restored after being deletion. Exercise caution when you perform this operation.
CCE enables you to quickly upgrade applications by replacing images or image versions without interrupting services.
To replace an image or image version, you need to upload the image to the image repository in advance. For more information, see Uploading a Private Image from the Internet and Uploading a Private Image from an Intranet.
Privileged containers have super permissions that are not available to regular containers. For example, privileged containers can use network devices on the host machine and modify the host's kernel parameters.
Parameter |
Description |
---|---|
Lifecycle |
Commands that are executed in each lifecycle phase of an application.
|
Health Check |
Set the health check function that checks whether containers and services are running properly. Two types of probes are set: application liveness probe and application service probe. For more information, see
Checking the Health of Containers.
|
Environment Variables |
Environment variables are set in the container running environment and can be modified after application deployment to ensure the flexibility of applications. You can set environment variables as follows:
|
Data Storage |
|
Security Context |
Set container permissions to protect CCE and other containers from being affected. Enter a user ID. The container will run with this user ID. |
Log Policies |
This parameter cannot be updated. |
After an application is created, you can go to the Monitoring page to monitor the CPU usage and memory usage of the container in which the application resides.
CCE needs time to compute CPU usage. Therefore, when CPU and memory usage are displayed for the first time, CPU usage is displayed about one minute later than memory usage
CPU and memory usage are displayed only for instances in the running state.
Labels are attached to applications using key-value pairs. Applications with labels attached can be easily selected for setting affinity and anti-affinity scheduling rules. You can add labels to multiple applications or a specified application.
In the following figure, three labels release, env, and role are defined for the applications APP1, APP2, and APP3. The values of these labels vary with applications.
If you set key to role and value to frontend when using application scheduling or another function, the function will apply to APP1 and APP2.
A key-value pair must start and end with a letter or digit and consist of a maximum of 63 characters, including letters, digits, hyphens (-), underscores (_), and periods (.).