Skip to content

Clarify GCS bucket permission requirements in SFT and RL tutorials#4098

Open
shralex wants to merge 1 commit into
mainfrom
shralex_ux2
Open

Clarify GCS bucket permission requirements in SFT and RL tutorials#4098
shralex wants to merge 1 commit into
mainfrom
shralex_ux2

Conversation

@shralex
Copy link
Copy Markdown
Collaborator

@shralex shralex commented Jun 6, 2026

Updates the SFT and RL multi-host tutorials to recommend either the broader Storage Admin role, or combining the restrictive Storage Object Admin role with Storage Legacy Bucket Reader. This ensures JAX/TensorStore can perform bucket-level operations (like storage.buckets.get) and prevents misleading 'bucket not found' errors.

FIXES: b/520780283

Checklist

Before submitting this PR, please make sure (put X in square brackets):

  • I have performed a self-review of my code. For an optional AI review, add the gemini-review label.
  • I have necessary comments in my code, particularly in hard-to-understand areas.
  • I have run end-to-end tests tests and provided workload links above if applicable.
  • I have made or will make corresponding changes to the doc if needed, including adding new documentation pages to the relevant Table of Contents (toctree directive) as explained in our documentation.

Updates the SFT and RL multi-host tutorials to recommend either the broader Storage Admin role, or combining the restrictive Storage Object Admin role with Storage Legacy Bucket Reader. This ensures JAX/TensorStore can perform bucket-level operations (like storage.buckets.get) and prevents misleading 'bucket not found' errors.
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.

1 participant