{"id":"gke-security-requires-naming-discipline-and-dual-governance","text":"GKE workload security requires mastery of two orthogonal dimensions: naming-dependent identity isolation where namespace/service-account conventions determine IAM identity across clusters (creating cross-cluster identity collisions from naming mistakes), AND the platform's dual IAM/CMEK control planes where access governance and data governance operate independently — making GKE security simultaneously a function of team naming discipline and architectural control-plane design.","truth_value":"OUT","source":"","source_url":"","source_hash":"","justifications":[],"dependents":[],"metadata":{"_retracted":true},"explanation":{"steps":[{"node":"gke-security-requires-naming-discipline-and-dual-governance","truth_value":"OUT","reason":"retracted premise"}]}}