GKE clusters should have resource labels
This control ensures that GKE clusters have resource labels. Kubernetes Clusters must be configured with labels, which means the attribute `resource_labels` must be defined. Labels make it easier to manage assets.
Labels make it easier to manage assets and differentiate between clusters and environments, allowing the mapping of computational resources to the wider organisational structure.
What this control checks
GKE clusters must define resource_labels
Common pitfalls
The resource_labels attribute must be defined
Kubernetes Clusters must be configured with labels, which means the attribute resource_labels must be defined.
Audit evidence
Evidence that deployed resources meet this control: PowerPipe control gcp_compliance.control.kubernetes_cluster_with_resource_labels.
Scans of the Terraform code that flag the same setting before deployment: Checkov check CKV_GCP_21; KICS query "Cluster Labels Disabled" (65c1bc7a-4835-4ac4-a2b6-13d310b0648d); Trivy check GCP-0051.
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
kubernetes_cluster_with_resource_labels - Checkov Check:
CKV_GCP_21 - Powerpipe Control:
gcp_compliance.control.kubernetes_cluster_with_resource_labels - KICS Query:
65c1bc7a-4835-4ac4-a2b6-13d310b0648d - Trivy Check:
GCP-0051
Last reviewed: 2026-10-09