Managing Workloads and Jobs

Scenario

Monitoring a Workload

You can view the CPU and memory usage of Deployments and pods on the CCE console to determine the resource specifications you may need. This section uses a Deployment as an example to describe how to monitor a workload.

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. Click the Deployments tab and click Monitor of the target workload. On the page that is displayed, you can view CPU usage and memory usage of the workload.
3. Click the workload name. On the Pods tab page, click the Monitor of the target pod to view its CPU and memory usage.

Viewing Logs

You can view logs of Deployments, StatefulSets, DaemonSets, and jobs. This section uses a Deployment as an example to describe how to view logs.

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. Click the Deployments tab and click the View Log of the target workload.

   On the displayed View Log window, you can view logs by time.

Upgrading a Workload

You quickly upgrade Deployments, StatefulSets, and DaemonSets on the CCE console.

This section uses a Deployment as an example to describe how to upgrade a workload.

Before replacing an image or image version, upload the new image to the SWR service.

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. Click the Deployments tab and click Upgrade of the target workload.
   

   • Workloads cannot be upgraded in batches.
   • Before performing an in-place StatefulSet upgrade, you must manually delete old pods. Otherwise, the upgrade status is always displayed as Upgrading.

3. Upgrade the workload based on service requirements. The method for setting parameter is the same as that for creating a workload.
4. After the update is complete, click Upgrade Workload, manually confirm the YAML file, and submit the upgrade.

Editing a YAML file

You can modify and download the YAML files of Deployments, StatefulSets, DaemonSets, and pods on the CCE console. YAML files of jobs and cron jobs can only be viewed, copied, and downloaded. This section uses a Deployment as an example to describe how to edit the YAML file.

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. Click the Deployments tab and choose More > Edit YAML in the Operation column of the target workload. In the dialog box that is displayed, modify the YAML file.
3. Click Edit and then OK to save the changes.
4. (Optional) In the Edit YAML window, click Download to download the YAML file.

Rolling Back a Workload (Available Only for Deployments)

CCE records the release history of all Deployments. You can roll back a Deployment to a specified version.

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. Click the Deployments tab, choose More > Roll Back in the Operation column of the target workload.
3. Switch to the Change History tab page, click Roll Back to This Version of the target version, manually confirm the YAML file, and click OK.

Redeploying a Workload

After you redeploy a workload, all pods in the workload will be restarted. This section uses Deployments as an example to illustrate how to redeploy a workload.

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. Click the Deployments tab and choose More > Redeploy in the Operation column of the target workload.
3. In the dialog box that is displayed, click Yes to redeploy the workload.

Disabling/Enabling Upgrade (Available Only for Deployments)

Only Deployments support this operation.

• After the upgrade is disabled, the upgrade command can be delivered but will not be applied to the pods.

  If you are performing a rolling upgrade, the rolling upgrade stops after the disabling upgrade command is delivered. In this case, the new and old pods co-exist.

• If a Deployment is being upgraded, it can be upgraded or rolled back. Its pods will inherit the latest updates of the Deployment. If they are inconsistent, the pods are upgraded automatically according to the latest information of the Deployment.

Deployments in the disable upgrade state cannot be rolled back.

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. Click the Deployments tab and choose More > Disable/Enable Upgrade in the Operation column of the workload.
3. In the dialog box that is displayed, click Yes.

Managing Labels

Labels are key-value pairs and can be attached to workloads. Workload labels are often used for affinity and anti-affinity scheduling. You can add labels to multiple workloads or a specified workload.

You can manage the labels of Deployments, StatefulSets, and DaemonSets based on service requirements. This section uses Deployments as an example to describe how to manage labels.

In the following figure, three labels (release, env, and role) are defined for workload APP 1, APP 2, and APP 3. The values of these labels vary with workload.

• Label of APP 1: [release:alpha;env:development;role:frontend]
• Label of APP 2: [release:beta;env:testing;role:frontend]
• Label of APP 3: [release:alpha;env:production;role:backend]

If you set key to role and value to frontend when using workload scheduling or another function, APP 1 and APP 2 will be selected.

Figure 1 Label example

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. Click the Deployments tab and choose More > Manage Label in the Operation column of the target workload.
3. Click Add, enter a key and a value, and click OK.
   

   A key-value pair must contain 1 to 63 characters starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.

Deleting a Workload/Job

You can delete a workload or job that is no longer needed. Deleted workloads or jobs cannot be recovered. Exercise caution when you perform this operation. This section uses a Deployment as an example to describe how to delete a workload.

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. In the same row as the workload you will delete, choose Operation > More > Delete.

   Read the system prompts carefully. A workload cannot be recovered after it is deleted. Exercise caution when performing this operation.

3. Click Yes.
   

   • If the node where the pod is located is unavailable or shut down and the workload cannot be deleted, you can forcibly delete the pod from the pod list on the workload details page.
   • Ensure that the storage volumes to be deleted are not used by other workloads. If these volumes are imported or have snapshots, you can only unbind them.

Viewing Events

This section uses Deployments as an example to illustrate how to view events of a workload. To view the event of a job or cron jon, click View Event in the Operation column of the target workload.

1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
2. On the Deployments tab page, click the target workload. In the Pods tab page, click the View Events to view the event name, event type, number of occurrences, Kubernetes event, first occurrence time, and last occurrence time.
   

   Event data will be retained for one hour and then automatically deleted.