Quickly Deploying an Application in Kubernetes (CCE Cluster)

Action Name

Custom action name. Enter 1 to 128 characters. Do not start or end with a space. Use letters, digits, spaces, and these special characters: -_,;:./()

Tenant

• Current: The software package is deployed in a CCE cluster of the current tenant for release.

  Select Current in this practice, your tenant must have the CCE cluster operation permission. If your tenant does not have such permission, enable the IAM authorization function below and select an authorized user.

• Other: The software package is deployed and released in a CCE cluster of another tenant in IAM authorization mode.

  After selecting Other, select an authorized tenant.

IAM authorization

If you do not have the permission to call CCE APIs, enable this option to obtain the temporary AK/SK of an authorized user.

Region

Select the region to be deployed.

Cluster Name

Select the Kubernetes cluster applied for on CCE.

Namespace

Select the namespace of the Kubernetes cluster on CCE.

Workload

Select the target workload to be deployed.

Only Deployment workloads are supported.

Instances

Enter the number of instances to deploy the workload to.

Container

Select the name of the CCE container to deploy the workload to.

Image

Select the image for deployment.

Image Tag

Select the tag of the image for deployment.

Container Specifications

Configure the specifications of the target container in the target workload.

• CPU Quota
  • Request: Minimum number of CPU cores required by a container. Resources are scheduled for the container based on this value. The container can be scheduled to a node only when the total available CPU on the node is greater than or equal to the requested quota.
  • Limit: Maximum number of CPU cores required by a container. If the CPU usage is greater than the limit, the CPU resources used by the container may be limited.
• Memory Quota
  • Request: Minimum memory size required by a container. Resources are scheduled for the container based on this value. The container can be scheduled to a node only when the total available memory on the node is greater than or equal to the requested quota.
  • Limit: Maximum memory size available for a container. When the memory usage exceeds the configured memory limit, the instance may be restarted, affecting normal use of deployment.

Environment Variables

Configure environment variables for the target container in the target workload.

Real-time environment variables are synchronized from CCE to replace the variables on this page.

Java Probes

Locate workload issues and analyze performance bottlenecks. For details, see Configuring APM.

Probe Type

• APM 2.0 Probe: Java probes will allocate 0.25-core CPU and 250-MiB memory to initialize containers.
• Disable: Probe-based fault locating is disabled.

When Probe Type is set to APM 2.0 Probe, configure the following parameters:

Probe Version: Select a probe version.

Probe Upgrade Policy: Select Automatic upgrade upon restart or Manual upgrade upon restart.

• Automatic upgrade upon restart: The system downloads the image upon each restart.
• Manual upgrade upon restart: If a local image is available, it will be used. If no local image is available, the system downloads the probe image.

APM Environment: (Optional) Enter the APM environment information.

APM Business: Select an APM application

APM Sub-Business: (Optional) Enter a sub-application.

Access Key Id: The system automatically obtains the relevant secret access key from APM. Go to the APM console to check the key details.

For details about the APM 2.0 parameters, see APM parameters.

Action Control

Continue the task even if this action fails.

Overtime

Maximum execution duration of the action, in minutes. If the duration exceeds the specified time before you stop the action, the action will be timed out. Value range: 1–30.