A cluster foundation
A fictional platform request specifies private nodes and a project workload pool. Private nodes do not, by themselves, establish a private control-plane endpoint. A workload pool also doesn’t grant every application access to its data. Open the GKE configuration lesson and inspect the requested fields. Explain which separate endpoint and principal bindings need review. This local cluster record does not schedule Pods or execute a control plane.
Nodes and application evidence
The console stores one node-count value. Native regional clusters and node pools have more detailed placement and count semantics; inspect the actual zones before making a capacity claim. A saved count doesn’t prove sufficient requests, scheduling or healthy application behavior.
Use the Kubernetes course for its supported workload, probe and rollout tasks. The Google Cloud course connects cluster decisions with IAM, network and log evidence. These are independent local environments, not a shared live GKE account.