GCP Kubernetes cluster node auto-repair configuration disabled misconfiguration detected in code

Rule Details

Cortex AppSec Rule ID	APPSEC_GCP_9
Category - Subcategory	Kubernetes - Resource Management
Provider	GCP
Severity	LOW
Framework	Terraform, Terraform Plan
Mapped CSPM/KSPM Rule	6769e686-5e96-4f67-8985-2646f9d90f1b

Impact

Auto-repairing mode in GKE is an automated service that identifies and repairs a failing node to maintain a healthy running state. GKE makes periodic checks on the health state of each node in the cluster. If a node fails consecutive health checks over an extended time period, GKE initiates a repair process for that node. We recommend automatic node repair is enabled on kubernetes clusters to provide continued operation of mission critical nodes and ensuring applications are operating based on their pre-defined specs, minimized downstream failures and redundant alerting and triage.

How to Fix

Add the following code bloc into your google_container_node_pool resource:

---

management { auto_repair = true }

If you don't have a separated node-pool resource on your terraform codebase, you can refer to the Gcloud CLI part. You will first need to recover the name of the node pool through the console or the CLI. Please be reminded that it is best practice to delete the default node-pool from the cluster and to create a specific one using the google_container_node_pool resource. More information here: https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-repair