docs: document GCP service account workload identity connection#292
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
GKestenberg
reviewed
May 28, 2026
GKestenberg
approved these changes
May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new
gcpServiceAccountservice connection, which binds a Porter service to a GCP IAM service account via GKE Workload Identity so pods can call GCP APIs without managing key files.Changes
porter.yamlaccordion.gcpServiceAccountexample to the connections section of the porter.yaml reference.Context
Triggered by porter-dev/code#5774, which introduced the GKE Workload Identity connection type end-to-end (proto contract, API, dashboard config, reconciler) under the new
gcpServiceAccountconnection name with a singleserviceAccountEmailfield. Porter creates theroles/iam.workloadIdentityUserbinding on the IAM service account at deploy time; users must pre-provision the service account and grant it the IAM roles it needs.