Enter the CCSE console, select a cluster in the cluster tab to enter the cluster details page. Select Workload > Stateless > Add. Choose the default namespace to create a Deployment.
Configuration Item Descriptions
Parameter | Description |
Deployment Name | Workload Name |
Volumes (optional) | Provide storage for containers, currently supporting temporary path, host path, configuration file, Local PV, NFS, Ceph, which also need to be mounted to a specified path in the container. |
Number of Instances | The number of replicas of the workload, which can be manually set or autoscaled. |
Instance Containers | The container instance configuration in the workload, which can be configured as one or more. |
Container Name | Container Instance Name |
Image and Image Version | Support choosing images from the CCR enterprise version or the CCR personal version. |
CPU/Memory Limits | Requests are used for pre-allocating resources. If the nodes in the cluster cannot provide the resource quantity requested, the container creation will fail. Limit sets the maximum resource usage for the container, preventing excessive resource consumption on nodes under abnormal circumstances. |
Environment Variables (optional) | Support the configuration of container environment variables. |
Startup Execution (optional) | Start the - command: ENTRYPOINT command of the image. The ENTRYPOINT command of the image is overwritten. Enter only one command or parameter in each input field Start the - parameter: CMD command of the image. The CMD command of the image is overwritten. Enter only one command or parameter in each input field |
Post-startup Processing | Run the command after the container is started. Since it is executed asynchronously, the command may not be always run after the ENTRYPOINT command. Enter only one command or parameter in each input field |
Pre-stop Processing | Execute this command before the container stops. It is commonly used for cleaning resources. Enter only one command or parameter in each input field |
Container Health Check | Liveness Check: It checks if the container is running properly; if not, the instance will be restarted. Readiness Check: It checks if the container is ready; if not, traffic forwarding to the current instance will be stopped. |
Privileged Containers | If a container runs in the privileged mode, it is granted the root privileges of the host. |
Container Security Context | Setting up the Security Context for the Container is applicable only to this Container. If users, user groups, and Selinux context are set at both the Pod and Container levels, the Container settings will overwrite the Pod settings. |
Access Setup | Configuring Service Access Load |