# Calico (/docs/foundation/components/calico)



## Component Category [#component-category]

Networking / network policy enforcement

## Component Description [#component-description]

Calico is a Kubernetes networking and network security project. BullSequana AI uses it only as a network policy engine: it enforces Kubernetes `NetworkPolicy` resources on a cluster whose network plugin does not. The Tigera operator installs and runs Calico from an `Installation` resource.

## Why It Is Used [#why-it-is-used]

In BullSequana AI Foundation, Calico gives sites a supported way to make the platform's NetworkPolicies effective. The platform renders allow and default-deny policies for its components and tenant namespaces, and they restrict traffic only where a policy engine enforces them. Calico is one such engine; Cilium or a provider-managed engine are alternatives.

## Learn More [#learn-more]

* [Calico documentation](https://docs.tigera.io/calico/latest/about/)
* [projectcalico/calico on GitHub](https://github.com/projectcalico/calico)

## Deployment notes [#deployment-notes]

Calico is a bootstrap release, not a GitOps application. A platform operator installs it with the platform CLI in two steps, the operator first, because the `Installation` resource needs the operator's CRDs:

```bash
bsqai helm-apply calico
bsqai helm-apply calico-installation
```

Both releases run Calico v3.33 in the `tigera-operator` namespace and pull their images from the platform registry. `push-manifests` never pushes them to the GitOps repository, but it warns when an installed release no longer matches the configuration. See [helm-apply](/docs/deployment/platform-cli#helm-apply).

The `calico-installation` component configures policy-only mode for AKS with Azure CNI: `[spec] kubernetes_provider = "AKS"` and `cni_type = "AzureVNET"`. The cluster's own network plugin keeps pod networking, and Calico adds enforcement. The Tigera operator refuses a provider other than the one it detects, and accepts `AzureVNET` only on AKS. The Calico API server and the Goldmane and Whisker flow-log components are not deployed.

The platform never applies its default-deny policy to the Calico operator namespace. To check with real traffic that the cluster enforces network policies, run [`bsqai test-npe`](/docs/deployment/platform-cli#test-npe). See [Network policies](/docs/deployment/configuration-model#network-policies) for the policies Calico enforces.

## Interacts With [#interacts-with]

* `Kubernetes`, whose NetworkPolicy resources Calico enforces next to the cluster's network plugin.
* `BSQAI Tenant Operator`, `Kyverno`, and the platform components, whose NetworkPolicies take effect once Calico runs.
* `Platform CLI`, which installs and checks the two Calico releases.
