Foresight is delivered as part of the Glasswall Halo CDR engine and is **disabled by default**.

This page covers deploying and enabling Foresight on a managed Kubernetes Halo deployment (AKS, EKS, GKE or OKE).


## Prerequisites

- **Halo version 2.19.0** - a Halo release that includes Foresight. See [v2.19.0 release notes](/halo/v2190).
- **Foresight entitlement**—a Halo license that includes the Foresight entitlement (`Glasswall Halo: Foresight`). If the entitlement is missing or invalid, Halo continues to process files normally and Foresight results are reported as unavailable.


## Deploying Foresight

Foresight is enabled through the `foresight.enabled` Helm value on the engine, which defaults to `false`. Enable it by upgrading the `cdrplatform-engine` release with the value set to `true` (see [Halo configuration changes](/halo/glasswall-halo-configuration-changes)):

```bash
helm upgrade --install cdrplatform-engine cdrplatform-engine --reuse-values --set foresight.enabled=true
```

If you are deploying Halo for the first time, set the same value as part of the standard deployment for your cloud provider in the [deployment](/halo/glasswall-halo-deployment-overview) section. No other Foresight-specific deployment steps are required.


### Disabling Foresight

To turn Foresight off again, upgrade the `cdrplatform-engine` release with `foresight.enabled=false`:

```bash
helm upgrade --install cdrplatform-engine cdrplatform-engine --reuse-values --set foresight.enabled=false
```

The engine pods roll to remove the Foresight sidecar; standard Glasswall CDR protection is unaffected.

## Verifying Foresight is deployed

After enabling Foresight and deploying or upgrading Halo:

- Confirm the engine pod is running and now includes the additional `foresight` container—for example, `kubectl get pods` should show an extra container in the engine pod, and the pod should become ready.
- The Foresight container runs a liveness health check; if it repeatedly fails, Kubernetes restarts the container.
- Foresight is **fail-open**: if the container is unavailable, Halo continues to process files and reports the Foresight result as unavailable, rather than blocking processing.

To confirm Foresight is producing results, process a supported file—PDF, DOCX or XLSX—and check that a Foresight result is returned. See [Configuring Foresight in Halo](/halo/configuring-foresight-in-halo) for how results appear and how to act on them.

## Next steps

- [Configuring Foresight in Halo](/halo/configuring-foresight-in-halo)