Open
Conversation
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
1 participant
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.
Note
Low Risk
Documentation-only change that clarifies authentication behavior for self-hosted GKE deployments; no runtime code changes.
Overview
Updates the Vertex AI integration docs to add a GKE Workload Identity Federation note: when
GCP_AUTH_MODE=workloadis enabled, the self-hosted Gateway auto-fetches Vertex AI access tokens from metadata so callers don’t need to pass anAuthorizationheader.Also documents the required IAM permission (
roles/aiplatform.user) for the Gateway’s bound GSA.Written by Cursor Bugbot for commit ba8fcff. This will update automatically on new commits. Configure here.