Docs/Administration/Corporate Root Certificates

Corporate Root Certificates

When a self-hosted deployment runs behind a proxy that inspects TLS and re-signs traffic with your company's root certificate, outbound calls from ANTS Platform fail with errors such as SELF_SIGNED_CERT_IN_CHAIN, UNABLE_TO_GET_ISSUER_CERT_LOCALLY or "unable to get local issuer certificate". This affects Microsoft Teams and Slack messages, SIEM push, support tickets, calls to LLM providers and model downloads.

The Helm value global.extraCaCerts adds your root certificate to every ANTS service at once. Public certificate authorities stay trusted, so hosts that are not behind the proxy keep working.

ℹ

This is a deployment setting for self-hosted Helm installs. It is off by default, and with it off the chart renders exactly as before. ANTS Cloud does not need it.

Add the root certificate

Get the root in PEM format

Use the root certificate of your proxy, not an intermediate. Convert a DER file first:

bash
openssl x509 -inform der -in root.cer -out root.pem

Add it to your values

yaml
global: extraCaCerts: enabled: true pem: | -----BEGIN CERTIFICATE----- <your root CA> -----END CERTIFICATE-----

Several roots can go in the same pem block.

Upgrade

Run helm upgrade with the new values. The chart creates one ConfigMap with the bundle in the platform namespace and mounts it read-only into every ANTS service.

Use a ConfigMap you already manage

If your security team distributes the root as a ConfigMap, point the chart at it instead of pasting the certificate. The ConfigMap must be in the ANTS platform namespace.

yaml
global: extraCaCerts: enabled: true existingConfigMap: name: corporate-root-ca key: ca.pem

The chart then creates no ConfigMap of its own.

ValueDefaultMeaning
global.extraCaCerts.enabledfalseTurns the feature on.
global.extraCaCerts.pememptyOne or more PEM root certificates.
global.extraCaCerts.existingConfigMap.nameemptyAn existing ConfigMap that holds the PEM bundle. Use this or pem, not both.
global.extraCaCerts.existingConfigMap.keyca.pemThe key in that ConfigMap.

Checks when rendering

The chart refuses to render, before anything is applied to the cluster, when:

  • it is enabled but neither pem nor existingConfigMap.name is set;
  • both are set;
  • pem has no -----BEGIN CERTIFICATE----- block;
  • pem contains a private key.

Rotate a root

  • Inline pem: change the value and run helm upgrade. The ANTS services restart and pick up the new root.
  • Your own ConfigMap: update it, then restart the ANTS deployments, for example with kubectl rollout restart deploy -n <namespace>.

How services trust it

Service typeHow the root is added
Node.js services (web, worker, gateway, connectors and others)NODE_EXTRA_CA_CERTS points at the mounted root.
Python services (guardrail, PII, bias and safety detection, and model serving)An ants-ca-bundle init container joins the image's public CA bundle and your root, and SSL_CERT_FILE and REQUESTS_CA_BUNDLE point at the result.

To check a running service, open a shell in the web deployment and confirm that echo $NODE_EXTRA_CA_CERTS prints a path and that the file at that path starts with -----BEGIN CERTIFICATE-----.

Limits

  • The database migration job does not use the bundle; it only reaches databases inside your network.
  • Third-party subcharts that ANTS does not build, such as ClickHouse, are not changed.
  • Trace worker jobs started at runtime outside the chart do not get the bundle in this release.
  • Proxy routing itself (for example HTTPS_PROXY) is not part of this setting.
© 2026 ANTS Platform, Inc.Docs v1.0 · Last updated June 2026