Why can permission to create pods in the kube-system namespace amount to full cluster compromise?

Pod creation implies the ability to set `serviceAccountName` to any account in the namespace — and kube-system hosts controllers with near-admin RBAC. The attacker pod simply reads the mounted token and uses it. This is a classic RBAC escalation path.