Roll Back to a Named Revision
The checkout-web Deployment in namespace ledgers has been changed several times this week, and each rollout was recorded with a change cause. Since then, latency has crept up. The team traced it back and decided to return to the state recorded as "enable response caching", discarding every change made after it.
checkout-web is identical to the revision whose change cause is enable response caching: same image and same environment variables.3 replicas are updated and available.A practice cluster is running on this machine: start with kubectl rollout history deploy/checkout-web -n ledgers.
About this machine
Ubuntu 24.04 with a private practice cluster: a real Kubernetes API server, scheduler and controllers, and three nodes (controlplane, node01, node02). Containers are simulated, so images never download and kubectl logs/exec are not available. k is an alias for kubectl, with completion. The grader checks the cluster's final state, not the commands you typed.
Your machine is ready to start
Create a free account to open a machine and get graded.