b10x-loom-operator

Generated from the clap definition of the b10x-loom-operator command line in crates/loom-operator/src/cli.rs by loom-docs. It lists only commands that exist.

The Kubernetes controller of the LoomAgent resource: each resource runs as one checked agent pod

b10x-loom-operator --version prints its version, and --help after any command prints the text below.

Commands

Command	What it does
b10x-loom-operator run	Watch the LoomAgent resources of the configured namespace and reconcile each into its ServiceAccount, ConfigMap, Deployment (a Job for a command), NetworkPolicy and Service, publishing its lifecycle as its status
b10x-loom-operator render	Print the children of one LoomAgent document as one multi-document YAML, after the checks the controller runs. Nothing is applied and no cluster is read
b10x-loom-operator crd	Print the LoomAgent CustomResourceDefinition, the bytes of deploy/crd/loomagents.loom.beyond10x.dev.yaml

b10x-loom-operator run

Watch the LoomAgent resources of the configured namespace and reconcile each into its ServiceAccount, ConfigMap, Deployment (a Job for a command), NetworkPolicy and Service, publishing its lifecycle as its status

Usage: b10x-loom-operator run --config <FILE>

Argument	Required	Default	Meaning
--config <FILE>	yes	none	The controller's configuration, YAML: namespace, defaultImage, defaultResources, defaultCommandResources, modelRoute, allowedSecretNames, allowedEgressHosts, allowedClaimNames, allowUnconfinedProfiles, allowedSeccompLocalhostProfiles, allowedAppArmorLocalhostProfiles, allowedBoundaryUpstreams

The configuration names the one namespace watched, the default agent image and resources, the
model route a resource with empty routes is given, the Secret names and egress hosts a resource may
use, and the upstreams a credential-free resource's boundary may relay to. The cluster is the
in-cluster service account's, else the current kubeconfig context's.
Each resource is checked in-process before any child exists; a refused one has no children and its
status names the refusal. The record of the resources lives in memory: after a restart every
resource is checked again and its status rewritten.

Exit status:
  0  the watch ended on a signal
  1  the configuration, the plugin catalog or the cluster connection cannot be read
  2  the command line is not valid

b10x-loom-operator render

Print the children of one LoomAgent document as one multi-document YAML, after the checks the controller runs. Nothing is applied and no cluster is read

Usage: b10x-loom-operator render [OPTIONS] --resource <FILE>

Argument	Required	Default	Meaning
--resource <FILE>	yes	none	One LoomAgent document, YAML or JSON
--config <FILE>	no	none	The controller's configuration, as run reads it; the built-in one without it

The resource's namespace is its metadata.namespace, else the configuration's. Without --config the
built-in configuration applies: namespace default, the agent image registry.example/loom-agent at
this version, 250m CPU and 256Mi memory for an AgentServe resource, no default size for a Command
resource (one without spec.agent.deploy.kubernetes.resources is refused ResourcesRequired), no
model route, and no Secret name, egress host or boundary upstream admitted.
The children carry the resource as owner only when the document has a metadata.uid.

Exit status:
  0  the children, as one multi-document YAML on standard output
  3  refused: standard error carries "refused: <reason> at <member>: <detail>"
  1  a file cannot be read, or the plugin catalog cannot be loaded
  2  the command line is not valid, or the document is not a LoomAgent

b10x-loom-operator crd

Print the LoomAgent CustomResourceDefinition, the bytes of deploy/crd/loomagents.loom.beyond10x.dev.yaml

Usage: b10x-loom-operator crd