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 (lcft, lcfc, lcf-api)

Encrypted

mTLS, certificates issued by cert-manager from the cluster CA, rotated automatically

Telemetry from the daemons

Encrypted

mTLS to the collector, terminated by each daemon's Envoy sidecar

lcf-api access

Authenticated

JWT bearer tokens with role-based authorization

Observability UI

Authenticated

Per-installation seeded admin credential, forced change at first login

Data at rest (KV cache on lcft devices)

Available, not enabled

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

Cluster-internal, unauthenticated

Plaintext ingest on a ClusterIP-only port, admitted from any in-cluster source by default so that multi-node vLLM ranks running with hostNetwork reach it. Never exposed on a node port. Restrict it with lcf-observability.networkPolicy.otlpFromCidrs and otlpPlaintextFromNamespaces — see the Hardening Checklist below.

Certificate lifecycle, expiry checks, and rotation are covered in Troubleshooting.

Decide on data-at-rest encryption before loading data

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.

The RDMA data path is authenticated, not encrypted

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

  1. Set lcf-observability.service.type=ClusterIP unless you deliberately want the dashboard on a node IP.

  2. Change the seeded observability admin password at first login, and keep the lcf-observability-admin Secret restricted.

  3. Set lcf-observability.networkPolicy.otlpFromCidrs to 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.

  4. Restrict lcf-observability.networkPolicy.otlpPlaintextFromNamespaces to the namespaces that actually serve vLLM — it is an unauthenticated port. This takes effect once step 3 is done.

  5. Use --ca-file with lcf-cli, never --insecure-skip-tls-verify, outside a lab.

  6. If you need data-at-rest encryption, arrange it before loading production data.