Force disabling of File Threat Protection

In Kaspersky Container Security 1.2, you can completely disable the File Threat Protection component. This can be necessary if you experience problems with the component.

You can forcibly disable the File Threat Protection component in two ways—by modifying the file for deploying agents on the cluster, and by modifying running agents.

To forcibly disable File Threat Protection using an agent deployment file:

1. Open the .YAML file with instructions for deploying agents on the cluster that you downloaded when you deployed the agents.
2. In the DaemonSet section for the node-agent, set the FILE_THREAT_PROTECTION_ENABLED environment variable to false.

   name: FILE_THREAT_PROTECTION_ENABLED

   value: false

3. Save changes to the instructions file.
4. In the console, apply the instructions file by running kubectl apply -f agents.yaml

   The orchestrator redeploys the node-agent pods with File Threat Protection disabled.

To forcibly disable File Threat Protection when agents are running:

1. In the console, open running agents using the kubectl edit command.
2. In the DaemonSet section for the node-agent, set the FILE_THREAT_PROTECTION_ENABLED environment variable to false.

   name: FILE_THREAT_PROTECTION_ENABLED

   value: false

3. Save your changes.

   The orchestrator applies the saved changes and disables File Threat Protection.