Configuring frontend mutual TLS (mTLS) on the GKE Gateway controller enables zero-trust client authentication directly at the Google Cloud Load Balancing (GCLB) edge before traffic reaches backend workloads. By referencing a ConfigMap containing your trusted client-issuing CA certificates, you can enforce strict client certificate validation across Global External ALBs, Regional External ALBs, and Regional Internal ALBs. Furthermore, GCLB can forward verified client certificate metadata—such as SPIFFE IDs, Subject Alternative Names (SANs), SHA-256 fingerprints, and certificate chains—directly to downstream pods via custom HTTP headers. This guide provides deployment manifests and verification commands using curl, jq, and openssl to test and validate frontend mTLS connections.
See the full guide and example manifests for GKE Gateway Frontend mTLS on GitHub.