docs(deployment): document multi-cloud object storage for langfuse and drop minio references - #329
Open
pavlochaikivskyi wants to merge 8 commits into
Open
docs(deployment): document multi-cloud object storage for langfuse and drop minio references#329pavlochaikivskyi wants to merge 8 commits into
pavlochaikivskyi wants to merge 8 commits into
Conversation
…d drop minio references
PR Preview Ready!Your preview documentation is ready! Visit it here: Preview URL: http://codemie-docs-pr-previews.s3-website.eu-central-1.amazonaws.com/pr-329/ This preview will be automatically updated when you push new commits to this PR. |
Expands the Object Storage step to cover IRSA as the recommended EKS auth method, with a note that IRSA is not supported by Langfuse for Azure Blob or GCS (static credentials required for those providers).
…d drop minio references Co-Authored-By: Claude <noreply@anthropic.com>
Add dedicated GCS Workload Identity section to deployment-prerequisites, replacing the incorrect "static credentials required" claim. Separate Azure and GCS (non-GKE) static-creds paths into their own sections. Update manual-deployment secret comment to clarify WI skips the secret. Co-Authored-By: Claude <noreply@anthropic.com>
…ent script Add GKE Workload Identity as a skip path for the object storage secret prompt, alongside IRSA. Clarify GCS static-creds as non-GKE fallback. Co-Authored-By: Claude <noreply@anthropic.com>
…on gke Remove the incorrect "static credentials required" claim for GCS. Document Workload Identity as the recommended path on GKE, with static service-account JSON as the non-GKE fallback. Co-Authored-By: Claude <noreply@anthropic.com>
elluvium
reviewed
Jul 29, 2026
|
|
||
| - **AWS EKS with IRSA** (recommended): type `y`. The pod's IAM role grants S3 access; no secret is needed. Verify that `langfuse.langfuse.serviceAccount.annotations` in `values.yaml` contains the correct IRSA role ARN (output `LANGFUSE_AWS_ROLE_ARN` from `deployment_outputs.env`). | ||
| - **GKE with Workload Identity** (recommended for GCS): type `y`. The pod's GCP service account grants GCS access; no secret is needed. Verify that `langfuse.langfuse.serviceAccount.annotations` in `values.yaml` contains the correct `iam.gke.io/gcp-service-account` annotation and `s3.gcs.credentials: {}` is set. | ||
| - **Azure Blob Storage**: type `N`. Enter the Storage Account name as the access key ID and the Storage Account key as the secret. |
Collaborator
There was a problem hiding this comment.
Could you add an explanation about why N is required for Azure. It's not clear at all. Also such type of instructions of "what to type" I would avoid. It would be better to rephrase at all this statements explaining exactly what happened and why instead of directing user what to type.
elluvium
reviewed
Jul 29, 2026
| storageProvider: "gcs" | ||
| bucket: "your-bucket-name" | ||
| gcs: | ||
| credentials: {} # empty → uses Workload Identity / ADC |
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
2 participants
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
langfuse-s3secret/example with thelangfuse-object-storagesecret shape (AWS S3 / Azure Blob / GCS).Test plan
npm run lint/npm run typecheckpass