SE-Radio Episode 319: Nicole Hubbard on Migrating from VMs to Kubernetes

Topics covered
Popular Clips
Episode Highlights
Seamless Transitioning
Ensuring a seamless transition from virtual machines to Kubernetes is crucial for WP Engine. explains that during the migration, both infrastructures run simultaneously for a brief period to ensure no impact on customers. This dual operation allows for a rollback if any issues arise, maintaining service continuity 1. The migration focuses on moving PHP processing to Kubernetes, utilizing PHP FPM with a Go wrapper, which offers better security and resource management compared to Apache 2.
We spin up the infrastructure in Kubernetes to do the PHP processing for that set of installs and then once that's running we reconfigure those sites to then process there and it's completely transparent.
---
This approach ensures that the migration is transparent to users, with no noticeable changes in their service experience.
Validation Process
The validation process is a critical step in WP Engine's migration to Kubernetes. outlines a two-step validation process that occurs before and after the migration to ensure the site functions correctly 3. Automated scripts, developed in Python, facilitate this process by checking the homepage for errors and ensuring consistent performance post-migration. Additionally, the use of multiple cloud providers like AWS and Google Cloud ensures regional availability, addressing global application challenges 4.
We wrote automated scripts around it and those provide the ability for us to move an entire virtual machine with a simple command.
---
This meticulous validation ensures that any potential issues are identified and resolved promptly, minimizing disruption.
Risk Management
Risk management is a pivotal aspect of WP Engine's migration strategy. describes a phased approach, starting with low-risk personal plans before gradually migrating larger business and enterprise customers 5. This strategy minimizes risk by allowing the team to identify and address issues early in the process. Additionally, internal accounts are used for initial testing to catch potential problems before affecting real customers 6.
We like to validate things with internal accounts before we ever put customers on them to ensure that we've caught the vast majority of any problems.
---
This careful planning and testing ensure a smooth transition with minimal risk to customer operations.
Related Episodes


SE Radio 619: James Strong on Kubernetes Networking
Answers 383 questions

SE-Radio Episode 270: Brian Brazil on Prometheus Monitoring
Answers 383 questions

SE-Radio-Episode-259:-John-Purrier-on-OpenStack
Answers 383 questions

SE-Radio Episode 344: Pat Helland on Web Scale
Answers 383 questions

SE Radio 649: Lukas Gentele on Kubernetes vClusters
Answers 383 questions

SE Radio 591: Yechezkel Rabinovich on Kubernetes Observability
Answers 383 questions

SE Radio 634: Jim Bugwadia on Kubernetes Policy as Code
Answers 383 questions

SE Radio 631: Abhay Paroha on Cloud Migration for Oil and Gas Operations
Answers 383 questions

SE Radio 600: William Morgan on Kubernetes Sidecars and Service Mesh
Answers 383 questions

SE-Radio-Show-246:-John-Wilkes-on-Borg-and-Kubernetes
Answers 383 questions

SE-Radio Episode 290: Diogo Mónica on Docker Security
Answers 383 questions

SE-Radio Episode 268: Kief Morris on Infrastructure as Code
Answers 383 questions

SE Radio 571: Jeroen Mulder on Multi-Cloud Governance
Answers 383 questions

SE-Radio 341: Michael Hausenblas on Container Networking
Answers 383 questions














