Calico

Optional network policy engine that enforces the platform's Kubernetes NetworkPolicies on clusters without one.

Agentic Friendly

Component Category

Networking / network policy enforcement

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

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

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:

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.

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. See Network policies for the policies Calico enforces.

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.

On this page