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 – Enable Private Nodes
- GKE – Restrict Control Plane Access
- GKE – Enable Workload Identity
- GKE – Disable Legacy ABAC
- GKE – Enable Network Policy
- GKE – Enable Shielded Nodes
- 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 Node Auto-Upgrade and Auto-Repair
Secure Configuration Checks > GCP
This check ensures that every Standard node pool in a Google Kubernetes Engine (GKE) cluster has node auto-upgrade and auto-repair enabled. Auto-upgrade keeps nodes aligned with supported Kubernetes versions and applies scheduled updates. Auto-repair detects unhealthy nodes and automatically replaces them. Autopilot clusters manage node upgrades and repairs automatically.
Check Details
- Resource: GKE Cluster
- Check: Enable node auto-upgrade and auto-repair
- Risk: Without automatic upgrades, nodes may continue running outdated Kubernetes versions and miss important security updates. Without automatic repair, unhealthy nodes may remain in the cluster, potentially affecting workload availability and reliability.
Remediation via Google Cloud Console
-
Log in to the Google Cloud Console and navigate to
Kubernetes Engine > Clusters.
- Click the affected Standard GKE cluster.
-
Locate the Node pools section and select the
node pool that requires configuration.
- On the node pool details page, click Edit.
- Under Management, enable both Enable auto-upgrade and Enable auto-repair.
-
Click Save to apply the changes.
- Repeat these steps for every Standard node pool in the cluster.
Note: Autopilot clusters automatically manage node upgrades and repairs. These settings cannot be disabled or manually configured for Autopilot nodes. If the node-pool management options are not available in your Console, use the Google Cloud CLI commands below.
Remediation via Google Cloud CLI
-
Open the Google Cloud Console and launch
Cloud Shell.
-
List the node pools that do not have both auto-upgrade and auto-repair enabled. The output shows the cluster, its location, the node pool, and the two settings:
gcloud container clusters list --format=json | jq -r '.[] | .name as $cluster | .location as $location | .nodePools[]? | select(((.management.autoUpgrade // false) | not) or ((.management.autoRepair // false) | not)) | [$cluster, $location, .name, (.management.autoUpgrade // false), (.management.autoRepair // false)] | @tsv' -
Enable auto-upgrade and auto-repair on the node pool:
gcloud container node-pools update <NODE_POOL_NAME> \ --cluster <CLUSTER_NAME> \ --location <LOCATION> \ --enable-autoupgrade \ --enable-autorepair
-
Verify the settings:
gcloud container node-pools describe <NODE_POOL_NAME> \ --cluster <CLUSTER_NAME> \ --location <LOCATION> \ --format="yaml(management)"
Replace
<NODE_POOL_NAME>with the name of the node pool,<CLUSTER_NAME>with the name of your GKE cluster, and<LOCATION>with its region or zone. The output must showautoRepair: trueandautoUpgrade: true. Repeat steps 3 and 4 for every node pool that step 2 lists. Auto-upgrade restarts nodes in a rolling update, so set a maintenance window and enough surge capacity, and make sure your workloads tolerate nodes being replaced.
Default Value
Auto-upgrade and auto-repair are enabled by default on new node pools. They can be turned off on older Standard node pools. Autopilot clusters manage their nodes automatically.
Updated on 09 November, 2026