A cloud engineer is configuring command-line administration and compute resources for a stateless, fault-tolerant batch data processing pipeline on Google Kubernetes Engine (GKE). The target cluster `analytics-batch-cluster` is deployed in region `us-central1`. Which TWO configuration steps must the engineer perform?
- Execute `gcloud container clusters get-credentials analytics-batch-cluster --region us-central1` to populate local kubeconfig authentication context.Answer
- Provision a dedicated node pool utilizing Spot VMs for batch workloads and ensure pod specifications contain tolerations for node preemption taints.Answer
- CRun `gcloud config set container/cluster analytics-batch-cluster` to point `kubectl` to the target cluster API server.
- DSelect GKE Autopilot cluster mode to allow custom node kernel sysctl modifications and custom host driver installations.
Answer
The correct configuration steps are to execute `gcloud container clusters get-credentials analytics-batch-cluster --region us-central1` to set up kubeconfig credentials, and to provision a Spot VM node pool with pod preemption tolerations for fault-tolerant batch processing.
To establish control plane access, `gcloud container clusters get-credentials` must be executed to populate local `kubeconfig` entries. For cost-effective batch computing, Spot VM node pools paired with pod preemption tolerations provide the recommended Google Cloud pattern for fault-tolerant workloads.
Step-by-Step Solution
Key Concept
GKE Cluster Credential Retrieval and Node Pool Workload Optimization