Skip to content

docs: document per-node-group GKE Workload Identity toggle#300

Open
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/f2aa8b03
Open

docs: document per-node-group GKE Workload Identity toggle#300
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/f2aa8b03

Conversation

@mintlify
Copy link
Copy Markdown
Contributor

@mintlify mintlify Bot commented May 28, 2026

Summary

Documents the new per-node-group Enable Workload Identity toggle for GKE clusters, which lets operators opt individual node pools into running the GKE metadata server so pods can impersonate GCP IAM service accounts.

Changes

  • Added a GKE Workload Identity (GCP) section to the Node groups page explaining when to use the toggle and how to enable it.
  • Rewrote the GCP section of Secure cloud access to reflect that GKE Workload Identity is now the supported path, with step-by-step setup (enable on the node group, create a GCP service account, attach to the service).

Context

Upstream PR exposes a enableWorkloadIdentity switch in both the application and user node group forms, shown only for GCP clusters. The toggle is required for any Porter service that needs to authenticate to GCP APIs via a service account connection.

@mintlify
Copy link
Copy Markdown
Contributor Author

mintlify Bot commented May 28, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
porter 🟢 Ready View Preview May 28, 2026, 11:11 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants