Platform & Reference·Last Verified: 2026-07-14
Exit Codes & Error Taxonomy
Understand CLI exit codes and platform stage failure codes.
To enable automation and reliable agent interaction, Kubeletto uses explicit exit code definitions and domain-specific stage errors.
CLI Exit Codes
| Code | Taxonomy | Trigger |
|---|---|---|
| 0 | Success | Finished successfully. |
| 1 | General Error | Unclassified runtime error. |
| 2 | Misuse / Validation | Invalid flags or parameters. |
| 3 | Unauthenticated | Expired session or invalid key. |
| 4 | Forbidden | Insufficient permissions. |
| 5 | Not Found | Resource does not exist. |
| 6 | Conflict | Resource already exists or state conflict (e.g. duplicate name). |
| 7 | Quota Exceeded | Exceeded allocated limits. |
| 8 | User Build Error | Code compile failed. |
| 9 | Platform Error | Internal cluster, network, or server error. |
| 10 | Timeout | Deploy watch timed out. |
| 11 | Cancelled | Command aborted by the user (e.g. declined a confirmation prompt). |
Platform Failure Stage Codes
IMAGE_NOT_FOUND: Container reference does not exist in registry.IMAGE_PULL_BACKOFF: Registry pull failed repeatedly (bad credentials or transient registry error).UNSUPPORTED_ARCH: Target image is not x86-64 (amd64).GIT_CLONE_FAILED: Cannot fetch files from remote repository.PORT_MISMATCH: Application failed to listen on port $PORT.CONTAINER_CRASH_LOOP: Runtime crashed repeatedly at launch.OOM_KILLED: Exceeded container memory threshold limits.READINESS_TIMEOUT: App started but never passed its readiness health check.
Was this helpful?