Feb 21
Loading video player...
Deploying a bad version to production is every engineer's nightmare. But in Kubernetes, you have the power to stop the damage and revert in seconds. In this tutorial, we dive deep into the kubectl rollout command suite to save your cluster from bad deployments. What you will learn: Detect: How to spot a failing deployment before it hits all users. Pause: Stop Kubernetes from pushing more "bad" pods. Undo: Instant rollback to the last known stable version. History & Revisions: How to jump back to a specific point in time. Prevention: Pro-tips on progressDeadlineSeconds and dry-run to avoid future downtime. Key Commands Covered: kubectl rollout status kubectl rollout pause/resume kubectl rollout undo --to-revision=X kubectl rollout history kubectl apply --server-dry-run Timestamps: 0:00 - Intro: Why you need kubectl rollout 0:05 - Step 1: Detecting a Bad Rollout (Status & Pods) 0:30 - Step 2: Pausing the Rollout to Limit Damage 0:55 - Step 3: Rolling Back to the Previous Version 1:20 - Step 4: Rolling Back to a Specific Revision 1:45 - Step 5: Resuming & Preventing Future Bad Versions #Kubernetes #DevOps #CloudNative #K8s #kubectl #SRE #Programming #SoftwareEngineering