Instant Single-Command Rollbacks
Revert buggy deployments instantly to the last healthy version in under a second.
The Problem
Fixing bugs under pressure or rebuilding and push-deploying emergency patches takes minutes while your site remains down.
The Kubeletto Solution
Kubeletto keeps all historical deployment revisions intact, allowing you to instantly repoint traffic to a working release.
Key Benefits & Workflow
Why Developers Prefer It
- Sub-second rollback: instantly switch DNS traffic routing back to a healthy build.
- Zero rebuild downtime: no compilations or Docker builds required.
- Version history tracking: view all deployed versions, authors, and commits.
How It Works
- 1
Identify a buggy deployment in your version history.
- 2
Select a previous stable release (e.g., Revision 4).
- 3
Click Rollback (or run the CLI command) to instantly restore traffic to that revision.
Under the Hood
Kubeletto keeps historic Knative Services active. A rollback simply updates the Knative Route resource to allocate 100% of traffic to the chosen healthy revision.
Managed container orchestration layer.
kubeletto rollback --revision rev_12345abcd --app frontend-serviceFrequently Asked Questions
Does rollback affect database state?
No. Rollbacks only revert container runtime code and variables, not external databases. Make sure migrations are backward-compatible.
Can I keep multiple versions active?
Canary deployments and user-managed traffic splitting are planned for a future release. Currently, only one active revision receives traffic, with instant rollback to previous versions.