Isolating Containers
Abnormal pods can be isolated and isolated pods cannot communicate with other resources.
Precautions
The privileged containers, node-started containers, security containers, and pause application containers cannot be isolated.
Procedure
1. Log in to the CSG Console.
2. Select Container security > Real-time monitoring on the left navigation bar to go to theReal-time monitoring page.
3. Click "Isolate the Pod" in the operation column on the right side of the container list.
4. In the dialog box that appears, enter the description information.
5. Click "Confirm" and isolate the container.
Restarting the Pod
After restart, the abnormal pod can be killed, and a new pod can be restarted through the k8s mechanism.
Procedure
1. Log in to the CSG Console.
2. Select Container security > Real-time monitoring on the left navigation bar to go to the Real-time monitoring page.
3. Click "Restart the Pod" in the operation column on the right side of the container list.
4. In the dialog box that appears, click "Confirm" .
Pausing Containers
Precautions
Stopped containers and history containers cannot be paused.
Procedure
1. Log in to the CSG Console.
2. Select Container security > Real-time monitoring on the left navigation bar to go to the Real-time monitoring page.
3. You can pause abnormal containers by clicking the pause button in the operation column on the right side of the container list.
Related Operation
Restoring a container to the running status: You can click the restore button in the operation column to restore the running status of a paused container.