An enterprise DevOps team is planning compute resources on Google Cloud for two distinct application components. Component 1 consists of a specialized network proxy service that requires custom Linux kernel module modifications. Component 2 consists of multiple stateless REST API microservices packaged in standard Docker containers, where the team wants to eliminate cluster node management overhead. Which compute architecture should the team select to fulfill these requirements?
- Deploy Component 1 on Compute Engine virtual machine instances and Component 2 on Google Kubernetes Engine (GKE) Autopilot clusters.Answer
- BDeploy Component 1 on Google Kubernetes Engine (GKE) Autopilot clusters and Component 2 on Compute Engine virtual machine instances.
- CDeploy Component 1 on Cloud Functions and Component 2 on Cloud Run.
- DDeploy both Component 1 and Component 2 on Cloud Run using custom container images.
Answer
Deploy Component 1 on Compute Engine virtual machine instances and Component 2 on Google Kubernetes Engine (GKE) Autopilot clusters.
Compute Engine provides full access to the underlying virtual machine operating system, allowing administrators to load custom kernel modules. GKE Autopilot manages cluster infrastructure and node scaling automatically, eliminating node management overhead for standard containerized microservices.
Step-by-Step Solution
Key Concept
Selecting GCP Compute Services Based on OS Customization Needs and Operational Overhead