Prerequisites

Everything on this page must be in place before either deployment path (lcf-cli or direct Helm) will succeed.

Required Tools for Deployment

Tool

Minimum version

Kubernetes

>= 1.28

Helm

>= 3.0

kubectl

>= 1.28

Install order

Before installing lcf-cli it is essential that Kubernetes and Helm are installed and operational.

Inferra Image Requirements

This page lists the container images required by the Inferra Helm chart and by lcf-cli deploy probe operations. Use it when preparing registry access, pull secrets, firewall allow lists, or offline image mirroring.

Release Registry

Cloudsmith release publishing mirrors the LCF-owned images below and stamps the release chart with:

global:
imageRegistry: "docker.cloudsmith.io/lightbits/lightbits-inferra"
imageTag: "vX.Y.Z"

LCF-owned images resolve to docker.cloudsmith.io/lightbits/lightbits-inferra/<repository>:<tag>.

Image

Default repository in source chart

Tag source

Used by

docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/lcft:vX.Y.Z

lcf/lcft

global.imageTag

lcft DaemonSet main container

docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/lcfc:vX.Y.Z

lcf/lcfc

global.imageTag

lcfc DaemonSet main container

docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/lcf-api:vX.Y.Z

lcf/lcf-api

global.imageTag

lcf-api Deployment main container

docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/k8s-bootstrap-and-sync:vX.Y.Z

lcf/k8s-bootstrap-and-sync

global.k8sBootstrapAndSyncImageTag, then global.deployerImageTag, then global.imageTag

TLS wait init containers, JWT bootstrap job, StepClusterIssuer bootstrap and cleanup jobs, CRD label hook job, Step-CA state restore and sync containers

docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/lcf-observability:vX.Y.Z

lcf/lcf-observability

global.imageTag

lcf-observability Deployment main container. Rendered when lcf-observability.enabled=true, which is the chart default.

For non-Cloudsmith source-chart renders, the same repositories render without a registry prefix and default to v1.0.0 unless global.imageRegistry and global.imageTag are set.

Third-Party Chart Images

These images are referenced directly by the chart and are not mirrored by the release workflow. Mirror them into the local registry when the cluster cannot pull from public registries.

Image

Used by

Notes

envoyproxy/envoy:v1.37.1

Envoy sidecars for lcft, lcfc, lcf-api, and lcf-observability

Terminates mTLS or JWT ingress and handles egress routing.

smallstep/step-ca:0.30.2

step-ca Deployment init and main containers

Can be disabled with step-ca.enabled=false when using an external Step-CA path supported by values.

cr.step.sm/smallstep/step-issuer:0.10.2

step-issuer Deployment

Rendered when stepIssuer.install=true.

quay.io/jetstack/cert-manager-cainjector:v1.20.2

Bundled cert-manager cainjector Deployment

Rendered when certManager.install=true and the chart manages bundled cert-manager.

quay.io/jetstack/cert-manager-controller:v1.20.2

Bundled cert-manager controller Deployment

Rendered when certManager.install=true and the chart manages bundled cert-manager.

quay.io/jetstack/cert-manager-webhook:v1.20.2

Bundled cert-manager webhook Deployment

Rendered when certManager.install=true and the chart manages bundled cert-manager.

quay.io/jetstack/cert-manager-acmesolver:v1.20.2

Referenced by cert-manager controller flag --acme-http01-solver-image

Pulled only if cert-manager creates HTTP-01 ACME solver pods. Inferra workload certificates use Step-CA, not ACME.

Observability Stack Images

The chart installs an observability stack by default: lcf-observability.enabled is true in charts/lcf/values.yaml, and lcf-cli deploy does not override it. Plan for these images on every install unless the stack is turned off.

The lcf-observability service image itself is LCF-owned and is mirrored by the release workflow; it is listed in the LCF-owned table above. The images below are third party and are not mirrored, so mirror them alongside the other third-party images for a private install.

Image

Used by

Notes

otel/opentelemetry-collector-contrib:0.119.0

OpenTelemetry collector container

Receives OTLP metrics and logs from the daemons and from the vLLM connector.

victoriametrics/victoria-metrics:v1.106.1

VictoriaMetrics container

Metrics storage and query.

victoriametrics/victoria-logs:v1.0.0-victorialogs

VictoriaLogs container

Log storage and query.

victoriametrics/vmalert:v1.106.1

vmalert container

Evaluates the shipped alerting rules.

prom/alertmanager:v0.27.0

Alertmanager container

Routes alerts. Rendered when alertmanager.enabled=true, the default.

To install without the stack, pass --set lcf-observability.enabled=false to lcf-cli deploy install, or set it in the values file for a direct Helm install. Doing so removes these five images and the lcf-observability image from the mirror set, and disables the Envoy sidecar for that pod.

lcf-cli Deploy Probe Images

lcf-cli deploy uses temporary probe workloads before or during installation.

Image

Default

Override

Used by

busybox:1.37

Yes

--probe-image

Device inventory DaemonSet lcf-device-probe, controlled by --probe-devices.

${registry}/lcf/k8s-bootstrap-and-sync:${tag}

Derived from install arguments

--registry, --tag, and --pull-secret

Registry preflight pull pod that validates image pull access before Helm runs.

The device probe DaemonSet is temporary. It runs one privileged pod per node, mounts host /sys and /proc read-only, writes the device inventory JSON to pod logs, and is deleted after collection. If --probe-devices=false, lcf-cli deploy skips this image and continues without device-level inventory.

lcf-cli diag collect (Troubleshooting) runs the same image, with the same --probe-image override, in its temporary host DaemonSet, lcf-diag-host-<run id>.

Minimum Image Mirror Set

For a fully private install with bundled cert-manager, bundled step-issuer, bundled Step-CA, and lcf-cli device probing enabled, mirror these images:

docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/lcft:vX.Y.Z
docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/lcfc:vX.Y.Z
docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/lcf-api:vX.Y.Z
docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/k8s-bootstrap-and-sync:vX.Y.Z
docker.cloudsmith.io/lightbits/lightbits-inferra/lcf/lcf-observability:vX.Y.Z
envoyproxy/envoy:v1.37.1
smallstep/step-ca:0.30.2
cr.step.sm/smallstep/step-issuer:0.10.2
quay.io/jetstack/cert-manager-cainjector:v1.20.2
quay.io/jetstack/cert-manager-controller:v1.20.2
quay.io/jetstack/cert-manager-webhook:v1.20.2
quay.io/jetstack/cert-manager-acmesolver:v1.20.2
otel/opentelemetry-collector-contrib:0.119.0
victoriametrics/victoria-metrics:v1.106.1
victoriametrics/victoria-logs:v1.0.0-victorialogs
victoriametrics/vmalert:v1.106.1

Trim the set to match what you actually enable:

If…

Remove from the mirror set

The cluster already provides cert-manager — set certManager.install=false

The four quay.io/jetstack/* images

Device probing is disabled with --probe-devices=false, and you will not collect host state with lcf-cli diag collect

busybox:1.37

The observability stack is disabled with lcf-observability.enabled=false

lcf/lcf-observability and the five observability third-party images