Using Shielded GKE Nodes

Autopilot Standard

---

This page shows you how to use the Shielded GKE Nodes feature. Shielded GKE Nodes provide strong, verifiable node identity and integrity to increase the security of Google Kubernetes Engine (GKE) nodes.

Note: For GKE Autopilot clusters, the Shielded GKE Nodes feature is enabled by default and cannot be overridden.

About Shielded GKE Nodes

Shielded GKE Nodes are built on top of Compute Engine Shielded VMs. Without Shielded GKE Nodes an attacker can exploit a vulnerability in a Pod to exfiltrate bootstrap credentials and impersonate nodes in your cluster, giving the attackers access to cluster secrets. When Shielded GKE Nodes is enabled, the GKE control plane cryptographically verifies that:

• Every node in your cluster is a virtual machine running in Google's data center.
• Every node is part of the Managed Instance Group (MIG) provisioned for the cluster.
• The kubelet is being provisioned a certificate for the node on which it is running.

This limits the ability of an attacker to impersonate a node in your cluster even if they are able to exfiltrate bootstrap credentials of the node.

You can optionally configure node integrity checks on node pools to provide enhanced rootkit and bootkit protection for your nodes. These node pool settings are independent from Shielded GKE Nodes and will work even if Shielded GKE Nodes is disabled on the cluster.

For more information, see the Shielded VM documentation.

There is no additional cost to run Shielded GKE Nodes. However, Shielded GKE Nodes generate about 0.5 KB more logs on startup than standard nodes. See the Cloud Logging pricing page for details.

Availability

Important: Starting with GKE version 1.18, newly created clusters will have Shielded GKE Nodes enabled by default.

• Shielded GKE Nodes are available in GKE version 1.13.6-gke.0 and later.
• Shielded GKE Nodes are available in all zones and regions.
• Shielded GKE Nodes can be used with all node images.
• Shielded GKE Nodes can be used with GPUs.

Warning: After you enable Shielded GKE Nodes in a cluster, any nodes created in a node pool without Shielded GKE Nodes enabled or created outside of any node pool aren't able to join the cluster.

Before you begin

Before you start, make sure you have performed the following tasks:

• Enable the Google Kubernetes Engine API.
Enable Google Kubernetes Engine API
• If you want to use the Google Cloud CLI for this task, install and then initialize the gcloud CLI.
  Note: For existing gcloud CLI installations, make sure to set the compute/region and compute/zone properties. By setting default locations, you can avoid errors in gcloud CLI like the following: One of [--zone, --region] must be supplied: Please specify location.

Enabling Shielded GKE Nodes in a new cluster

You can create a new cluster with Shielded GKE Nodes enabled by using the gcloud CLI or the Google Cloud console.

gcloud

When creating a new cluster, specify the --enable-shielded-nodes option:

gcloud container clusters create CLUSTER_NAME \
    --enable-shielded-nodes

Console

1. Go to the Google Kubernetes Engine page in the Google Cloud console.

   Go to Google Kubernetes Engine

2. Click Create.

3. From the navigation pane, under Cluster, click Security.

4. Select the Enable Shielded GKE Nodes checkbox.

5. Configure your cluster as desired.

6. Click Create.

See Creating a cluster for more details about creating clusters.

Enabling Shielded GKE Nodes in an existing cluster

You can enable Shielded GKE Nodes in an existing cluster by using the Google Cloud CLI or the Google Cloud console.

After you enable Shielded GKE Nodes, the control plane and nodes are recreated as Shielded VMs. The control plane is unavailable while it is being recreated. The cluster nodes are recreated in a rolling fashion to minimize downtime.

Warning: If you are using maintenance windows and are not in a maintenance window when you enable this feature, your control plane will be recreated immediately, but the nodes will not be recreated until a maintenance window occurs. This delay might caused failed node registrations and disruption to your cluster. To manually recreate the nodes as Shielded GKE Nodes, you must follow the instructions in node recreation and maintenance windows. Manually draining and deleting individual nodes does not recreate the nodes as Shielded GKE Nodes.

gcloud

When updating the cluster, specify the --enable-shielded-nodes option:

gcloud container clusters update CLUSTER_NAME \
    --enable-shielded-nodes

Console

1. Go to the Google Kubernetes Engine page in Google Cloud console.

   Go to Google Kubernetes Engine

2. Click the name of the cluster you want to modify.

3. Under Security, in the Shielded GKE Nodes field, click Edit Shielded GKE Nodes.

4. Select the Enable Shielded GKE Nodes checkbox.

5. Click Save Changes.

Verifying that Shielded GKE Nodes are enabled

You verify that your cluster is using Shielded GKE Nodes with the Google Cloud CLI or the Google Cloud console.

gcloud

Describe the cluster:

gcloud container clusters describe CLUSTER_NAME

If Shielded GKE Nodes are enabled, the output of the command will include these lines:

shieldedNodes:
  enabled: true

Console

To verify that a cluster is using Shielded GKE Nodes:

1. Go to the Google Kubernetes Engine page in Google Cloud console.

   Go to Google Kubernetes Engine

2. Click the name of the cluster you want to inspect.

3. Under Security, in the Shielded GKE Nodes field, verify that Shielded GKE Nodes is Enabled.

You can also monitor the integrity of your nodes' underlying Shielded VMs. See Monitoring Integrity on Shielded VM Instances for the procedure.

Disabling Shielded GKE Nodes

You can disable Shielded GKE Nodes with the Google Cloud CLI or the Google Cloud console.

Warning: If you are using maintenance windows, your nodes are not recreated until a maintenance window occurs. This delay might cause failed node registrations and disruption to your cluster. To minimize disruption, you can manually "upgrade" the node pool to the same version that it is already using, by setting the --cluster-version flag to the same GKE version that the control plane is already running. You must use the gcloud command if you use this workaround. For more information, see the caveats section of the maintenance window documentation.

gcloud

When updating the cluster, specify the --no-enable-shielded-nodes option:

gcloud container clusters update CLUSTER_NAME \
    --no-enable-shielded-nodes

Console

1. Go to the Google Kubernetes Engine page in Google Cloud console.

   Go to Google Kubernetes Engine

2. Click the name of the cluster you want to modify.

3. Under Security, in the Shielded GKE Nodes field, click Edit Shielded GKE Nodes.

4. Clear the Enable Shielded GKE Nodes checkbox.

5. Click Save Changes.

After you disable Shielded GKE Nodes, the control plane and nodes are recreated as ordinary, unshielded VMs. The control plane is unavailable while it is being recreated. The cluster nodes are recreated in a rolling fashion to minimize downtime.

Node integrity

Secure Boot and Integrity Monitoring are node pool settings that can be used alongside Shielded GKE Nodes. Shielded GKE Nodes, Secure Boot, and Integrity Monitoring are independent features that can each be enabled or disabled individually.

Secure boot

Secure boot is a node pool setting that's disabled by default on GKE because third-party unsigned kernel modules cannot be loaded when secure boot is enabled.

If you don't use third-party unsigned kernel modules, you can enable secure boot with the Google Cloud CLI or the Google Cloud console.

gcloud

To enable secure boot when creating a cluster:

gcloud container clusters create CLUSTER_NAME \
    --shielded-secure-boot

To enable secure boot when creating a node pool:

gcloud container node-pools create POOL_NAME \
    --shielded-secure-boot

Secure boot is disabled by default. You can explicitly disable it when creating a cluster or node pool with the --no-shielded-secure-boot option.

Console

To enable secure boot when creating a node pool:

1. Go to the Google Kubernetes Engine page in Google Cloud console.

   Go to Google Kubernetes Engine

2. Click the name of the cluster you want to modify.

3. Click Add Node Pool.

4. From the navigation menu, click Security.

5. Under Shielded options, select the Enable secure boot checkbox.

6. Click Create.

Integrity monitoring

Integrity monitoring is a node pool setting that's enabled by default on GKE. You can disable integrity monitoring with the Google Cloud CLI or Google Cloud console.

gcloud

To disable integrity monitoring for system components when creating a cluster:

gcloud container clusters create CLUSTER_NAME \
    --no-shielded-integrity-monitoring

To disable integrity monitoring for system components when creating a node pool:

gcloud container node-pools create POOL_NAME \
    --no-shielded-integrity-monitoring

Integrity monitoring is enabled by default. You can explicitly enable it when creating a cluster or node pool with the --shielded-integrity-monitoring option.

Console

To disable integrity monitoring when creating a node pool:

1. Go to the Google Kubernetes Engine page in Google Cloud console.

   Go to Google Kubernetes Engine

2. Click the name of the cluster you want to modify.

3. Click Add Node Pool.

4. From the navigation pane, click Security.

5. Under Shielded options, clear the Enable integrity monitoring checkbox.

What's next

• Learn more about Shielded VM.
• Learn more about node images.