Deploying an Application in Kubernetes (CCE Cluster) Using Manifest

Action Name

Manifest File Source

This parameter is mandatory. Artifact, Repo, or obs can be selected.

Repo

This parameter is mandatory when Manifest File Source is set to Repo.

This parameter is mandatory. Select the corresponding code repository.

Branch

This parameter is mandatory when Manifest File Source is set to Repo.

This parameter is mandatory. Select the corresponding branch.

Manifest File

This parameter is mandatory.

• If the Manifest File Source is Artifact or OBS, select the Manifest Files to be deployed. Files must be suffixed with .yaml, .yml, or .json.

  Click . On the file selection page that is displayed, select a Manifest File to be deployed in Artifact. By default, the project cannot be changed. You can search for the manifest file by keyword or upload the local manifest file to the repository, click , refresh the repository file, and select a manifest file. Click .

• If the Manifest File Source is Repo, enter file name suffixed with .yaml, .yml, or .json, and click to edit the file.

Tenant

This parameter is mandatory. There are two options:

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

  Select Current. The current tenant must have the CCE cluster operation permission. If the current tenant does not have the CCE cluster operation permission, select IAM authorization 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.

IAM authorization

This parameter is optional. 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 to be deployed.

Cluster Name

Select the Kubernetes cluster applied on CCE.

Namespace

Select the namespace of the Kubernetes cluster on CCE.

Java Probes

You can locate workload issues and analyze performance bottlenecks. For details, see Configuring APM Settings for Performance Bottleneck Analysis.

Probe Type

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

When Probe Type is set to APM2.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 existing APM service.

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

Access Key Id: The system automatically obtains the key information of APM. You can 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 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