Hi folks :wave: — I’m running GrowthBook on Kubern...
# ask-questions
d
Hi folks šŸ‘‹ — I’m running GrowthBook on Kubernetes and using GCS for uploads. Backend is configured with:
Copy code
UPLOAD_METHOD=google-cloud
GCS_BUCKET_NAME=growthbook-bkt
GCS access and Workload Identity are working (I can run
gsutil ls
successfully from the backend pod). However, when I try to upload a file from the web UI (e.g. in an experiment), I consistently get:
Copy code
Failed to upload file: Direct uploads are only supported for local storage. 
Use /upload/signed-url-for-upload for cloud storage.
From the backend logs I can see the frontend is calling:
Copy code
PUT /upload
and the backend responds with that error. Example log:
Copy code
method=PUT url=/upload
msg="Direct uploads are only supported for local storage. Use /upload/signed-url-for-upload for cloud storage."
So it looks like the UI is still attempting the legacy direct upload flow instead of calling:
Copy code
POST /upload/signed-url-for-upload
Backend and frontend image is
4.3.0
. Question: Is there any frontend config or version requirement to enable the signed-URL upload flow for GCS? Any pointers on what controls the switch away from
PUT /upload
would be really helpful. Thanks in advance.
s
Let me share this with the team.
thankyou 1