rune get

rune get <resource-type> [name] [flags]

Resource types

Type	Aliases	Notes
`services`	`svc`	Top-level workloads.
`instances`	`inst`	Running copies of services.
`namespaces`	`ns`	Logical scopes.
`jobs`		Batch workloads (roadmap).
`configs`		ConfigMaps.
`secrets`		Secrets (values redacted).
`storageclasses`	`sc`	Cluster-scoped storage classes.
`volumes`	`vol`	Persistent volumes.
`snapshots`	`snap`	Volume snapshots.

Examples

# List all services in the current namespace
rune get services

# Describe one in YAML
rune get service api -o yaml

# Across all namespaces
rune get services --all-namespaces

# Watch for live updates
rune get services --watch

# JSON for scripting
rune get instances -o json | jq '.[] | select(.status=="Running") | .id'

Flags

Flag	Default	Notes
`-n, --namespace`	context	Target namespace.
`-A, --all-namespaces`	false	List across every namespace.
`-o, --output`	`table`	`table`, `json`, `yaml`.
`--watch`	false	Stream updates as state changes.
`-l, --selector`	—	Label selector (e.g. `app=api,tier=frontend`).

Service detail view

rune get service <name> (singular) renders a paragraph view rather than a one-row table. It includes:

header line — <name> <namespace> <Status> for <age>
spec summary — image, scale, ready count, exposure + TLS state
failure block (only when Status: Failed) — short reason + the one-sentence message that explains it
per-instance breakdown — sorted failed-first, with the failing instance’s status message indented underneath
one hint command at the bottom

api  prod   Failed for 4m

  ghcr.io/acme/api:1.4.2 · scale 2 · 0/2 ready
  exposed at https://api.acme.io  ·  TLS Issued (in 89d)

  ✗ ImageUnreachable
    pull access denied for ghcr.io/acme/api, repository does not exist
    or may require 'docker login'

  Instances (2):
    ✗ api-7d9c-b2  node-edge-1   Failed   ×6
        pull access denied for ghcr.io/acme/api ...
    ✗ api-7d9c-a1  node-edge-2   Failed   ×6
        pull access denied for ghcr.io/acme/api ...

  rune logs api -n prod --tail=50

-o yaml and -o json still take the structured path.

REASON in the table

rune get services includes a REASON column between STATUS and READY. It’s - for healthy services and a short slug (ImageUnreachable, Unhealthy, Restarting, OutOfMemory, Unplaceable, ConfigMissing, LaunchFailed, Exited) for failed ones. To see the full sentence, run rune get service <name>.

Tips

rune get service <name> -o yaml round-trips into something you can edit and re-cast.
--watch is great for “what’s the rollout doing right now?” — Ctrl-C exits.
-o json plus jq is the scripting path. Don’t try to parse table output.