Config Connector is a Kubernetes integration that lets you declare Google Cloud resources as custom resources in a cluster. Instead of calling Google Cloud APIs directly, a user submits a manifest and the Config Connector controller reconciles that desired state using its own Google Cloud identity. This makes cloud infrastructure easier to automate, but it also means the controller becomes a powerful intermediary.
In security terms, Config Connector can create a confused deputy risk if the controller has more Google Cloud permissions than the person who authored the manifest. A low-privilege Kubernetes user may be able to influence resources outside their intended scope if RBAC, namespace boundaries, or controller permissions are too broad. Defenders should apply least privilege to the controller service account, tightly restrict who can create or edit Config Connector resources, and treat project, folder, or organization-scoped changes as high-risk actions that require review and monitoring.