# VPC Service Controls rules can name GKE workload identity principals

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Google Cloud added a preview on 14 October 2026 that lets VPC Service Controls ingress and egress rules use Workload Identity Federation for GKE principals. Rules can match all pods using a Kubernetes service account, all pods in a namespace, or all pods in a cluster.

Google Cloud published a VPC Service Controls entry dated 14 October 2026, marked Preview. It supports Workload Identity Federation for GKE in ingress and egress rules that allow access to resources protected by a service perimeter. The release note says the rules can name all GKE pods that use a Kubernetes service account, by name or ID, all pods in a Kubernetes namespace, or all pods in a cluster.

For anyone writing perimeter exceptions, this gives a way to describe a workload by where it runs in Kubernetes instead of only by a service account or an IP range. Because the feature is in Preview, Google has not marked it for production commitments yet. Teams should test it in dry run mode before relying on it.

## Related pages

- [VPC Service Controls violation analyzer adds remediation suggestions](/news/vpc-sc-remediation-suggestions-preview/)
- [Control Tower Account Factory for Terraform adds plan-only runs](/news/control-tower-aft-plan-only-customization-runs/)
- [IAM Identity Center adds network access controls for Identity Store](/news/identity-center-identity-store-network-access-controls/)
- [All of them](/news/)

## Sources

- https://cloud.google.com/vpc-service-controls/docs/release-notes (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/news/vpc-sc-gke-workload-identity-ingress-egress-rules/
