Other Articles
- Cloud SQL – Configure Private IP
- Cloud SQL – Monitor CPU Utilization
- Cloud SQL – Enable Deletion Protection
- Cloud SQL – Enable Disk Encryption
- Cloud SQL – Enable Automated Backups
- Cloud SQL – Enable Log Export
- Cloud SQL – Enforce Password Validation
- Cloud SQL – Protect From Internet Access
- Cloud SQL – Enforce Secure Transport
- Compute Engine – Block Project-Wide SSH Keys
- Compute Engine – Disable IP Forwarding
- Compute Engine – Disable Public IP Addresses
- Compute Engine – Disable Serial Port Access
- Compute Engine – Enable Confidential Computing
- Compute Engine – Enable OS Login
- Compute Engine – Enable Shielded VM
- Compute Engine – Restrict Default Service Account
- General – Deny Public Access to KMS Keys
- General – Enforce Duties Separation
- General – Enforce KMS Key Rotation
- General – Restrict Admin Roles on Service Accounts
- Cloud Run – Configure Timeout Settings
- Cloud Storage – Enable Bucket Encryption
- Cloud Storage – Enable Bucket Logging
- Cloud Storage – Enable Bucket Versioning
- Cloud Storage – Enforce Uniform Bucket-Level Access
- Cloud Storage – Restrict Public Access
- IAM Users – Enforce GCP-Managed Keys
- IAM Users – Rotate External User-Managed Service Account Keys
- GKE – Restrict Control Plane Access
- GKE – Enable Workload Identity
- GKE – Disable Legacy ABAC
- GKE – Enable Network Policy
- GKE – Enable Shielded Nodes
- GKE – Enable Node Auto-Upgrade and Auto-Repair
- GKE Cluster – Enable Cluster Logging
- General – Enable Cloud Audit Logs
- General – Configure a Log Sink
- General – Configure Log Bucket Retention
- Cloud SQL – Enable High Availability
- Cloud SQL – Configure Maintenance Window
- Cloud Storage – Configure Bucket Retention or Lifecycle
- General – Enable Security Command Center
- Compute Engine – Enable Instance Deletion Protection
- VPC Firewall – Restrict Public SSH and RDP Access
- VPC Firewall – Restrict Public Database Access
- VPC Network – Avoid the Default Network
- VPC Network – Enable Subnet Flow Logs
GKE – Enable Private Nodes
Secure Configuration Checks > GCP
This check ensures that the nodes of a Google Kubernetes Engine (GKE) cluster use private IP addresses. With private nodes, the worker machines have no public IP address and cannot be reached directly from the internet.
Check Details
- Resource: GKE Cluster
- Check: Enable private nodes
- Risk: If nodes have public IP addresses, attackers can scan and attack them directly from the internet, which increases the chance of a compromise of the cluster and its workloads.
Remediation via Google Cloud Console
-
Log in to the Google Cloud Console and navigate to
Kubernetes Engine > Clusters.
- Click the name of the affected GKE cluster.
- In the cluster details page, locate the Private Nodes section.
-
Under Default New Node-Pool Configuration,
click Edit Private Nodes.
- Select Enable private nodes.
-
Click Save changes to apply the configuration.
Remediation via Google Cloud CLI
-
Open the Google Cloud Console and launch
Cloud Shell.
-
List the GKE clusters that do not use private nodes:
gcloud container clusters list \ --filter="NOT privateClusterConfig.enablePrivateNodes=true" \ --format="table(name,location)"
-
Enable private nodes on the cluster:
gcloud container clusters update <CLUSTER_NAME> \ --location <LOCATION> \ --enable-private-nodes
-
Enable private nodes on each existing node pool:
gcloud container node-pools update <NODE_POOL_NAME> \ --cluster <CLUSTER_NAME> \ --location <LOCATION> \ --enable-private-nodes
-
Verify the setting:
gcloud container clusters describe <CLUSTER_NAME> \ --location <LOCATION> \ --format="value(privateClusterConfig.enablePrivateNodes)"
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 value in the last command must beTrue. Nodes without public IP addresses cannot reach the internet on their own, so set up Cloud NAT if your workloads need outbound internet access.
Default Value
By default, GKE nodes are created with public IP addresses. Private nodes are used only when they are explicitly enabled.
Updated on 09 November, 2026