Real LensAI Compose/env configuration vs design-target inferix.yaml control plane.

Configure the stack you can run: Compose env, Helm values, and flagd definitions. A unified inferix.yaml for a suite control plane is a design target — not a shipped config schema.

Shipped — lensai-integration

quickstart/docker-compose.yml — services, ports, healthchecks
quickstart/.env — e.g. EBPF_MOCK, rate limits, Kafka topic names
quickstart/flagd/flags.json — initial flag definitions

Entry: make build && make up. Docs: lensai-integration.

Shipped — infra-ai-streaming profiles

All deploy paths go through ./scripts/run.sh with a profile or custom values file.

# Profiles → Helm values / Compose env
m1       deploy/helm/lensai/values-m1.yaml      deploy/compose/values-m1.env
dev      deploy/helm/lensai/values-dev.yaml     deploy/compose/values-dev.env
default  deploy/helm/lensai/values.yaml
k3d      deploy/helm/lensai/values-k3d.yaml

Copy values.example.yaml for a custom cluster. See deploy/README.md.

Design target / not shipped The sketch below is the intended control-plane config shape for when a unified Inferix process exists. Mounting it at /etc/inferix/inferix.yaml does nothing until that binary ships.

# DESIGN TARGET — not a runnable config today
listen: ":4000"
master_key: ${INFERIX_MASTER_KEY}

models:
  - name: owned/general-llm
    provider: owned
    endpoint: http://general-llm:8080/v1

routing:
  default: owned/general-llm
  fallback: owned/general-llm

observe:
  lensai: true
  traces: true

drift:
  enabled: true
  window: 24h

Loop thesis and eng deep-links: Architecture. Product maturity: Status & maturity.

Secrets

Never commit real keys. Use Compose/Helm secrets and env files outside git for anything that can reach production systems.

Configuration

Shipped — lensai-integration

Shipped — infra-ai-streaming profiles

Target — inferix.yaml

On this page