trust-manager

Distributes CA trust bundles across namespaces for consistent TLS verification.

Agentic Friendly

Component Category

Access and security / certificate management

Component Description

trust-manager is a Kubernetes operator that distributes CA trust bundles as ConfigMap or Secret resources across namespaces. It uses a Bundle custom resource to define which CA certificates should be available and where they should be projected.

Why It Is Used

In BullSequana AI, trust-manager ensures that platform components share a consistent set of trusted CA certificates. This is required when the platform uses custom or internal CAs, because each component namespace needs access to the same trust bundle for TLS verification to succeed across service-to-service communication.

Learn More

Deployment notes

trust-manager v0.21 deploys into the cert-manager namespace at sync wave 3, the same wave as cert-manager. Because all dependent components are in higher sync waves, CA bundles are available before those components start.

Bundles

BundleSourcesTarget
ca-bundleThe default public CAs, the platform root and intermediate CAs, the custom wildcard certificate's CA when custom TLS is on, and the external S3 CA when one is configuredPlatform component namespaces only, as a Secret with key ca-certificates.crt and a PKCS#12 copy ca-certificates.p12, and as a ConfigMap with key ca.crt
kserve-cabundleThe same CAs, plus the shared model repository's CA when one is configuredEvery namespace labelled bsqai.io/model-serving: enabled, tenant serving namespaces included, as a ConfigMap with key cabundle.crt for the KServe storage initializer and vLLM

Tenant namespaces do not receive ca-bundle; a tenant serving namespace receives only kserve-cabundle. Kyverno mounts ca-bundle into opted-in pods of storage-client namespaces.

Interacts With

  • cert-manager, which manages the certificates whose CA chains trust-manager distributes. Both share the cert-manager namespace.
  • Platform components, which consume the projected ca-bundle for outbound TLS verification.
  • KServe, whose storage initializer and model servers read kserve-cabundle in each serving namespace.
  • Kyverno, which mounts ca-bundle into opted-in storage-client pods.

On this page