Kubernetes

Start from the reference manifest

Use the example manifest at fallbakit-agent.yaml.

ConfigMap values

Set the local runtime explicitly:

data:
  FALLBAKIT_BASE_URL: "https://api.fallbakit.com"
  FALLBAKIT_LOCAL_PROVIDER: "ollama"
  FALLBAKIT_LOCAL_BASE_URL: "http://ollama.default.svc.cluster.local:11434"
  FALLBAKIT_RUNNER_ID: "runner_from_dashboard"
  FALLBAKIT_METRICS_ADDR: ":9093"

For oMLX, keep the same manifest shape and change:

data:
  FALLBAKIT_LOCAL_PROVIDER: "omlx"
  FALLBAKIT_LOCAL_BASE_URL: "http://omlx.default.svc.cluster.local:8000"

For vLLM, point the base URL at the service origin without /v1:

data:
  FALLBAKIT_LOCAL_PROVIDER: "vllm"
  FALLBAKIT_LOCAL_BASE_URL: "http://vllm.default.svc.cluster.local:8000"

Secret

Store the runner API key in the Secret. If the local vLLM server requires an API key, store that separately as local-api-key:

stringData:
  runner-api-key: "rr_from_dashboard"
  local-api-key: "optional_vllm_api_key"

Apply

kubectl apply -f deployments/kubernetes/fallbakit-agent.yaml
kubectl rollout status deployment/fallbakit-agent

Verify

kubectl get pods
kubectl logs deploy/fallbakit-agent
kubectl port-forward deploy/fallbakit-agent 9093:9093
curl http://localhost:9093/readyz

Start from the reference manifest

ConfigMap values

Secret

Apply

Verify

On this page