Help Center> CodeArts Deploy> User Guide> Managing Applications> Deployment Actions> Deploying an Application in Kubernetes (CCE Cluster) Quickly
Updated on 2024-05-10 GMT+08:00
View PDF

Deploying an Application in Kubernetes (CCE Cluster) Quickly

This section introduces how to deploy an application quickly by upgrading Kubernetes workload images.

Prerequisites

A CCE cluster is available.

Procedure

Table 1 Parameters

Parameter

Description

Action Name

Name of an action displayed in the deployment actions area.

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

    Select Current tenant. The current tenant must have the CCE cluster operation permission. If the current tenant does not have the CCE cluster operation permission, select Authorized User for deployment.

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

    If you select Other, you must select an authorized tenant to deploy the CCE cluster.

NOTE:

Escalate privilege with IAM

If you do not have the permission to execute an API, this parameter enables you to obtain the temporary AK/SK of the parent user to execute the CCE API through IAM.

Region

Select the region for deployment.

Cluster Name

Select the Kubernetes cluster applied on CCE.

Namespace

Select the namespace of the Kubernetes cluster on CCE.

Workload

Select the target Deployment.

Pods

Enter the number of instances to be deployed.

NOTE:

If blank, the current number of pods in the CCE cluster will be adopted.

Container

Select the name of the CCE container to be deployed.

Image

Select the image to be deployed.

Image Tag

Select the tag of the image to be deployed.

Container Specifications

You can 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

You can configure environment variables of the target container in the target workload.

You can synchronize real-time environment variables from CCE to this page to replace current variables.

Java Probes

This helps you quickly locate workload issues and analyze performance bottlenecks. For details, see Configuring APM Settings for Performance Bottleneck Analysis.

Control Options

Continue the task even if this action fails.

Overtime

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

You can use ${XXX} to reference parameters Container, Image, Image Tag, Instances, and Java Probes (including APM Environment and APM Sub-Businesses). For operation details, see Parameter Management.

Parent topic: Deployment Actions