How Do I Use Events to Fix Abnormal Workloads?

Fault Locating

To check whether there is an abnormal pod in the workload, perform the following steps:

1. Log in to the CCE console.
2. Click the cluster name to access the cluster console. In the navigation pane, choose Workloads.
3. In the upper left corner of the page, select a namespace, locate the target workload, and view its status.
   • If the workload is not ready, view pod events and determine the cause. For details, see Viewing Pod Events.
   • If the workload is processing, wait patiently.
   • If the workload is running, no action is required. If the workload status is normal but it cannot be accessed, check whether intra-cluster access is normal.

     Log in to the CCE console or use kubectl to obtain the pod IP address. Then, log in to the node where this pod locates and run curl or use other methods to manually call the APIs. Check whether the expected result is returned.

     If {Container IP address}: {Port} cannot be accessed, log in to the service container and access 127.0.0.1: {Port} to locate the fault.

Viewing Pod Events

Method 1

On the CCE console, click the workload name to go to the workload details page, locate the row containing the abnormal pod, and click View Events in the Operation column.

Method 2

Run kubectl describe pod {Pod name} to view pod events. The following shows an example:

$ kubectl describe pod prepare-58bd7bdf9-fthrp
...
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  49s   default-scheduler  0/2 nodes are available: 2 Insufficient cpu.
  Warning  FailedScheduling  49s   default-scheduler  0/2 nodes are available: 2 Insufficient cpu.