Deploying Drupal without downtime sounds straightforward—until something goes wrong.
In this practical session, we’ll follow a Drupal release through its complete deployment lifecycle on Kubernetes: deploying a new version without interrupting users, deliberately introducing a broken release, investigating the failure, and safely rolling back to the previous stable version.
We’ll explore how Kubernetes rolling deployments, readiness and health checks can help keep Drupal available while a new release is introduced. Using prepared screenshots from a realistic deployment scenario, we’ll see what happens to old and new application instances during a deployment and how Kubernetes decides when a new version is ready to receive traffic.
Then we’ll break the release. We’ll investigate the problem using Kubernetes status, application health checks and Drupal logs before walking through the rollback and recovery process.
Attendees will leave with a practical understanding of how to make Drupal deployments safer, observable and recoverable while minimizing disruption to users.