Mountkirk Games is developing a new retro-style FPS game that allows hundreds of simultaneous players in geo-specific digital arenas and displays a global leaderboard. They plan to deploy the game's backend on Google Kubernetes Engine (GKE) and use Google's global load balancer to route players to the closest regional game arenas. To keep the global leaderboard in sync, they plan to use a multi-region Spanner cluster. The existing environment, recently migrated to Google Cloud, consists of isolated projects for new games and consolidated projects for legacy games, with separate environments for development and testing. The game must support multiple platforms, regions, and rapid iteration of features while minimizing latency, optimizing for dynamic scaling, using managed services, and minimizing costs. The technical requirements include dynamic scaling based on game activity, near real-time global leaderboard updates, structured log storage for future analysis, GPU processing for graphics rendering, and eventual migration of legacy games to the new platform. You need to implement a network ingress for this new game that meets these business and technical requirements and ensures each regional game instance is deployed in multiple Google Cloud regions. What should you do?