Tooling
quiltc
Quilt's control-plane CLI for clusters, nodes, workloads, and k8s workflows.
quiltc is Quilt’s control-plane CLI.
If the HTTP API is the engine, quiltc is a well-designed dashboard over that engine.
GitHub: ariacomputecompany/quiltc
What quiltc Is For
- create and inspect clusters
- mint join tokens
- register, heartbeat, drain, or delete nodes
- create, update, or delete workloads
- reconcile placements
- watch long-running operations
- validate, diff, and apply Kubernetes manifests against Quilt backend endpoints
Auth Inputs
QUILT_BASE_URL
QUILT_API_KEY
QUILT_JWT
QUILT_JOIN_TOKEN
Use QUILT_JOIN_TOKEN specifically for node registration flows.
Core Mental Model
- cluster = desired-state control plane
- node = participating host
- workload = replicated application spec
- placement = scheduler assignment
This matches the control-plane nouns from the cluster API page.
Common Flows
Behavioral Notes
quiltcwraps the platform over HTTP- do not assume local runtime CLIs are the canonical interface
applyanddiffrequire--cluster-idapplyvalidates first by default--dry-runonk8s applygives validate-plus-diff behavior without mutating backend state
Why People Like quiltc
It removes the little mistakes that hand-written HTTP calls often introduce:
- missing auth env vars
- wrong body shape
- missing registration fields
- forgetting to follow long-running operations
When to Use the CLI vs Raw HTTP
| Situation | Better choice |
|---|---|
| Repeated human workflows | quiltc |
| Scripting against the raw control plane | HTTP API |
| Learning the platform surface | both together |
A Very Practical Starting Point
1
Set your base URL and auth
2
Inspect the cluster surface
3
Try a runtime call too
4
Watch the returned operation
