Google Cloud wants to make leaving Amazon’s Kubernetes service less painful, and its new EKS-to-GKE migration agent does a fair amount of the tedious work. Google announced the tool on October 5 as part of Google Cloud Modernize, a bundle that pulls its migration and modernization services under one name. The agent is in public preview, so expect rough edges.
It scans an EKS cluster or source repository, finds application dependencies and AWS-specific settings, then generates Terraform modules for the Google Cloud side. It also translates AWS IAM Roles for Service Accounts into Google’s Workload Identity, maps Application Load Balancer ingress to the Kubernetes Gateway API, and converts Karpenter node configurations for GKE. Those are exactly the cloud-specific details that tend to eat weeks of an engineer’s time.
Still, Google drew a careful line around what the agent will not do. It never applies changes to a live GKE cluster. Instead, it opens pull requests, so the output travels through a team’s existing CI/CD and approval steps first. It also leaves stateful data alone, producing runbooks that point teams to Database Migration Service or Storage Transfer Service. Analysts cited by Network World add that application testing, architecture decisions, data migration and the final production cutover all stay outside its scope.
That division of labor is sensible. In my view, it is also the honest one, since the riskiest parts of any migration are the ones where a mistake costs real downtime. A tool that drafts the plumbing but asks for human sign-off on everything else is easier to trust.
Beyond the agent, the wider Modernize portfolio covers a lot of ground. Modernization Hub analyzes Java, .NET and mainframe code, and Migration Center now assesses more AWS services, from EC2 and DynamoDB to Kinesis and ElastiCache.
Pareekh Jain, a principal analyst at Pareekh Consulting, noted that teams juggling VMware, Java, mainframe, Oracle and Kubernetes have usually needed separate tools and separate crews. Google is pitching one front door as better than five. Whether customers believe the migration is truly easier will depend on how much of that final cutover work the agent eventually absorbs.
