From d0de3c052cc7eae8b605103c4d1a2769aa34cb0b Mon Sep 17 00:00:00 2001 From: Matthew Stevenson Date: Fri, 8 Aug 2025 23:16:02 +0000 Subject: [PATCH] Clarify use cases where gRPC's ALTS libraries are supported. --- layouts/shortcodes/docs/auth_alts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/layouts/shortcodes/docs/auth_alts.md b/layouts/shortcodes/docs/auth_alts.md index dceefda74e3..983e1576115 100644 --- a/layouts/shortcodes/docs/auth_alts.md +++ b/layouts/shortcodes/docs/auth_alts.md @@ -18,9 +18,9 @@ ALTS in gRPC has the following features: gRPC users can configure their applications to use ALTS as a transport security protocol with few lines of code. -Note that ALTS is fully functional if the application runs on +Note that ALTS is fully support for connections between GCP and Google if the application runs on [Compute Engine](https://cloud.google.com/compute) or -[Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine). +[Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine). ALTS does not support workload-to-workload authentication between GCP workloads. {{ with .Page.Params.code.client_credentials -}}