Other Articles

GKE – Enable Shielded Nodes

Secure Configuration Checks > GCP

This check ensures that the nodes of a Google Kubernetes Engine (GKE) cluster are Shielded GKE nodes with verified boot integrity. Shielded nodes check that a node starts from a trusted state and that nobody has tampered with its boot process. Autopilot clusters enforce this setting.

Check Details

  • Resource: GKE Cluster
  • Check: Enable shielded nodes
  • Risk: Without Shielded GKE Nodes, an attacker who obtains node bootstrap credentials may be able to impersonate a node and gain unauthorized access to cluster resources, including sensitive secrets. Shielded GKE Nodes help prevent this by verifying node identity before the control plane accepts a node.

Remediation via Google Cloud Console

  1. Log in to the Google Cloud Console and navigate to Kubernetes Engine > Clusters. GKE Clusters
  2. Click the affected GKE cluster.
  3. Under the Security section, locate Shielded GKE Nodes and click the Edit icon.
  4. Select Enable Shielded GKE Nodes and click Save Changes. GKE Enable Shielded Nodes
  5. Wait for the cluster update to complete. GKE recreates the worker nodes as Shielded VMs using a rolling update.

Additional recommendation: Google recommends enabling Secure Boot for all Standard cluster node pools and keeping Integrity Monitoring enabled. These are separate node-pool settings. Secure Boot should be tested with your workloads because it can prevent unsigned kernel modules from loading on Ubuntu nodes.

Remediation via Google Cloud CLI

  1. Open the Google Cloud Console and launch Cloud Shell. GCP Cloud Shell
  2. List the GKE clusters that do not have shielded nodes enabled:

    gcloud container clusters list \
    --filter="NOT shieldedNodes.enabled=true" \
    --format="table(name,location)"
    
  3. Enable shielded nodes on the cluster:

    gcloud container clusters update <CLUSTER_NAME> \
    --location <LOCATION> \
    --enable-shielded-nodes
    
  4. Turn on integrity monitoring for each existing node pool:

    gcloud container node-pools update <NODE_POOL_NAME> \
    --cluster <CLUSTER_NAME> \
    --location <LOCATION> \
    --shielded-integrity-monitoring
    
  5. Verify the settings:

    gcloud container clusters describe <CLUSTER_NAME> \
    --location <LOCATION> \
    --format="value(shieldedNodes.enabled)"
    
    gcloud container node-pools describe <NODE_POOL_NAME> \
    --cluster <CLUSTER_NAME> \
    --location <LOCATION> \
    --format="yaml(config.shieldedInstanceConfig)"
    

    Replace <CLUSTER_NAME> with the name of your GKE cluster, <LOCATION> with its region or zone, and <NODE_POOL_NAME> with the name of the node pool. The first command must return True, and the second must show enableIntegrityMonitoring: true. Updating the nodes recreates them in a rolling update, so test your applications before you change a production cluster. You can also add --shielded-secure-boot to the node pool command. Secure Boot blocks unsigned kernel modules, so test any workload that loads custom modules first.

Default Value

Shielded GKE nodes are enabled by default on new clusters. Older Standard clusters can have them turned off. Autopilot clusters always use shielded nodes.

Updated on 09 November, 2026