Country or region and language

    Choose your country or region and your language.

    Suggested for you

      All countries and regions

        Choose your character

        It shows in the top bar and on your profile. Change it any time.

        Google Kubernetes Engine and GKE practice

        Separate node addressing, control-plane access and workload identity before calling a cluster ready. Each is a different configuration boundary.

        Checked 14 November 2026

        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.

        Sources

        Your Work Gym account

        Save your progress and pick up on another device. Your browser's progress comes with you.

        or

        You can keep practicing without an account.

        Help and feedback

        Ask a question, tell us what is not working, or share an idea. We reply by email.

        What is it about?

        We use it only to reply to you.