Deployment Lifecycle

1ctl deploy converts project intent into backend deployment metadata and Kubernetes resources.

Current lifecycle

1ctl deploy
  |
  +- read satusky.toml and flags
  +- build image in-cluster unless --image is supplied
  +- upsert desired deployment state
  +- reconcile workload resources
  +- wait for pod readiness when --wait is set
  +- report public URL readiness separately when available

Resources

Typical deployment resources include:

• Deployment
• Service
• optional ConfigMap
• optional Secret
• optional PVC
• optional HPA / VPA / PDB
• public routing resource

Readiness

Readiness	Question
Build	Is there an image to run?
Workload	Are pods scheduled and ready?
Route	Does Kubernetes route the hostname to the Service?
DNS	Does the hostname resolve publicly?
TLS / HTTP	Does HTTPS serve the app?

These are separate states. --wait primarily proves workload readiness; domain diagnostics should be checked with 1ctl domains check.

Rollback

1ctl app releases lists deployment versions. 1ctl app rollback reconciles the deployment using an older version snapshot.