<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workload-Identity-Federation on RLGeeX</title><link>https://www.rlgeex.com/tags/workload-identity-federation/</link><description>Recent content in Workload-Identity-Federation on RLGeeX</description><generator>Hugo</generator><language>en-us</language><copyright>RLGeeX © 2025 - Real-Life Geeks providing expert IT consulting</copyright><lastBuildDate>Thu, 26 Feb 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://www.rlgeex.com/tags/workload-identity-federation/index.xml" rel="self" type="application/rss+xml"/><item><title>Credential isolation between clients on a shared GCP foundation</title><link>https://www.rlgeex.com/news/credential-isolation-between-clients-on-a-shared-gcp-foundation/</link><pubDate>Thu, 26 Feb 2026 09:00:00 -0500</pubDate><guid>https://www.rlgeex.com/news/credential-isolation-between-clients-on-a-shared-gcp-foundation/</guid><description>&lt;p>This post is for cloud engineers building a GCP foundation with Terraform that will host workloads for more than one client. Isolation between clients comes from giving each client principals and trust domains that cannot overlap. Naming conventions and the secrecy of identifiers do not provide it. If two clients&amp;rsquo; workloads can end up as the same IAM principal, IAM cannot tell them apart, and a role granted to one applies to both. Below is how I would lay out service accounts, keys and pools so they can&amp;rsquo;t overlap, and when you can relax.&lt;/p></description></item></channel></rss>