Skip to main content

Description

Show status for a model or a specific model release. With <name>:<release>, the report covers three facets:
  • Release: whether the release tag is registered and currently deployed
  • Image: whether a container image has been pushed via reactor model publish
  • Weights: whether weights have been uploaded via reactor weights upload
With <name> only, the report shows the model metadata and all registered releases, including deployment, image, and weights rollups. Pass -l for a per-region instance table (DESIRED/RUNNING/HEALTHY/IDLE) of the model’s live fleet. The table header names the currently-deployed release; the counts are not filtered by release. HEALTHY counts pods with a live runtime heartbeat (idle or serving), which is the signal a readiness probe cannot give for single-session model pods. A cell reads ”?” when the server did not report that count. “Instances: none” means no cluster reported live instances: the model may have no deployed release, the rollout may not have landed yet, or every Supervisor serving it failed to report. Use -o json|yaml for the same per-region data in a structured document. It names one release (the deployed one, or the newest when none is deployed) and reports instances as [] for an empty fleet, or null with instances_unavailable when the lookup failed. Both flags apply to the <name> form only. With no argument, the model name is inferred by walking up from the current directory to the nearest enclosing reactor.yaml (stopping at the repository root). Examples:

Options

Global options

See also