A telemetry analysis firm is planning its Google Kubernetes Engine (GKE) cluster strategy. The deployment includes two main workloads: a stateless front-end API service that requires zero node-level operational overhead, and an advanced packet-inspection engine that requires custom Linux kernel settings (sysctl parameters) at the node OS level. Which two architectural decisions should the infrastructure team implement to meet these requirements?
- Provision a GKE Autopilot cluster to host the stateless front-end API service.Answer
- Provision a GKE Standard cluster with customized node pool configurations for the packet-inspection workload.Answer
- CDeploy the packet-inspection workload into a GKE Autopilot cluster using privileged containers to modify host kernel sysctl parameters.
- DConfigure Spot VM node pools in GKE Autopilot to automatically enable custom OS kernel parameters for processing workloads.
- EDeploy a single GKE Standard cluster using Spot VMs for persistent storage databases to minimize compute costs.
Answer
The infrastructure team should provision a GKE Autopilot cluster to host the stateless API service, and provision a GKE Standard cluster with customized node pool configurations for the packet-inspection workload.
GKE Autopilot is designed for hands-off management of standard stateless applications where Google manages node provisioning and security. GKE Standard provides full control over node infrastructure, allowing custom OS system configurations such as custom sysctl parameters.
Step-by-Step Solution
Key Concept
Selecting between GKE Autopilot and GKE Standard based on node management overhead and node-level kernel customization requirements.