Deploying an Application in Kubernetes (CCE Cluster) Using Manifest

Action Name

Manifest File Source

Mandatory. Artifact, Repo, and OBS can be selected.

Repo

Mandatory when Manifest File Source is set to Repo.

Branch

Mandatory when Manifest File Source is set to Repo.

Manifest File

Mandatory.

• If Manifest File Source is set to Artifact or OBS, select a manifest file to be deployed. The file name 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 a local one to the repository, click to refresh repository files, and select the manifest file. Click .

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

Tenant

Mandatory. There are two options:

• 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

Optional. 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.

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.