API Reference · Workloads

Resource tree of a workload

The Kubernetes objects backing one workload — what a GitOps dashboard would show — read live from the cluster: Deployments, ReplicaSets, Pods, Services, PVCs, ConfigMaps, Secrets (**names only, never data**), Ingresses, IngressRoutes and (for VM workloads) VirtualMachineInstances, plus recent Events referencing them. The list is flat; rebuild the tree from `ownerKind`/`ownerName` (Deployment → ReplicaSet → Pod). Capped at 100 resources and 30 events (newest first). Kinds the platform can't read are skipped, never an error.

GET/v1/tenants/{name}/workloads/{id}/resources

Authorization

x-api-keystringrequired

Your per-workspace API key, e.g. llc_AbC123…. Also accepted as Authorization: Bearer <key>. Mint keys on your workspace's API keys page — each key belongs to one workspace.

Path parameters

namestringrequired

Workspace (tenant) name.

idstringrequired

Workload id within the workspace.

Response

200 — The workload's live resources and recent events.

resourcesarray

eventsarray

curl https://api.live-llm.com/v1/tenants/acme/workloads/web/resources \
  -H "x-api-key: $LIVELLM_KEY"

Try itGEThttps://api.live-llm.com/v1/tenants/{name}/workloads/{id}/resources

API keyYour key stays in your browser (saved locally on this device) and is sent only to the API.

name*id*

Fill required path params: name, id.

Example response200

{
  "resources": [
    {
      "kind": "Deployment",
      "name": "acme-web",
      "group": "apps",
      "status": "Running",
      "ready": true,
      "age": "4d",
      "ownerKind": "",
      "ownerName": "",
      "detail": "1/1 replicas ready"
    }
  ],
  "events": [
    {
      "type": "Normal",
      "reason": "Started",
      "message": "Started container web",
      "object": "pod/acme-web-6b9f",
      "age": "2m"
    }
  ]
}