Security
This page states what Inferra protects by default, and what it does not. Read it before exposing a cluster beyond a lab.
What Is Protected by Default
Surface | Default | Mechanism |
|---|---|---|
Control-plane gRPC ( |
| mTLS, certificates issued by cert-manager from the cluster CA, rotated automatically |
Telemetry from the daemons |
| mTLS to the collector, terminated by each daemon's Envoy sidecar |
|
| JWT bearer tokens with role-based authorization |
Observability UI |
| Per-installation seeded admin credential, forced change at first login |
Data at rest (KV cache on |
| Client-side AES-256-XTS, per-tenant key-encryption keys from an external KMS, per-namespace data keys distributed by the Coordinator. Requires a KMS — contact Lightbits Support to configure. |
Telemetry from the vLLM connector |
| Plaintext ingest on a ClusterIP-only port, admitted from any in-cluster source by default so that multi-node vLLM ranks running with |
Certificate lifecycle, expiry checks, and rotation are covered in Troubleshooting.
Configure data-at-rest encryption before loading production data if your deployment has that requirement. It is not something to switch on afterwards.
The connector's telemetry path is worth one note: pylcf runs inside the vLLM pod, which the serving fleet owns, so it cannot carry a client certificate and uses the plaintext ingest port described in Observability. Treat the cluster network between the vLLM pods and the collector as trusted, or leave connector telemetry off.
UCX exchanges certificates at connection setup, and the subsequent RDMA transfers are authenticated but not encrypted on the wire. A TCP/TLS 1.3 transport is available where the fabric is not trusted; discuss it with Lightbits Support.
Hardening Checklist
Set
lcf-observability.service.type=ClusterIPunless you deliberately want the dashboard on a node IP.Change the seeded observability admin password at first login, and keep the
lcf-observability-adminSecret restricted.Set
lcf-observability.networkPolicy.otlpFromCidrsto the CIDRs your nodes' traffic reaches pods from. The default admits any source on both OTLP ports: the mTLS port relies on the client certificate, the plaintext port on being reachable only inside the cluster.Restrict
lcf-observability.networkPolicy.otlpPlaintextFromNamespacesto the namespaces that actually serve vLLM — it is an unauthenticated port. This takes effect once step 3 is done.Use
--ca-filewithlcf-cli, never--insecure-skip-tls-verify, outside a lab.If you need data-at-rest encryption, arrange it before loading production data.