ork control — Orkestra

Manage the Orkestra Control Center (CC).

ork control [command]

The Control Center provides a web‑based UI for monitoring multiple Orkestra runtime instances.

Commands

Start the Orkestra Control Center.

ork control start [flags]

Flag	Description
`-p, --port <port>`	Port to run the Control Center on (default: `8081`)
`-u, --urls <list>`	Comma‑separated list of Orkestra runtime URLs (default: `http://localhost:8080`)
`--refresh <duration>`	Auto‑refresh interval for fetching Katalogs (default: `10s`)
`--log-level <level>`	Log level (`debug`, `info`, `warn`, `error`)
`-i, --ignore-default`	Do not add the default `localhost:8080` instance

Start with defaults:

ork control start

Custom port and multiple instances:

ork control start --port 9090 --urls "http://localhost:8080,http://localhost:8082"

Debug logging:

ork control start --log-level debug --refresh 5s

Remote runtimes:

ork control start --urls "https://prod.orkestra:8080,https://staging.orkestra:8080"

Show the installed Control Center version.

ork control version

ork control start locates the orkcc binary in:
- $PATH
- next to the ork binary
- ~/.orkestra/bin/
If not found, Orkestra attempts installation (placeholder logic until implemented).
The Control Center runs as a standalone binary (orkcc) and takes over the terminal.

ork control does not interact with Kubernetes directly.
It only manages the local Control Center binary.
Runtime URLs must point to running Orkestra runtime instances (ork run or deployed operators).