https://bentoml.com logo
Join Slack
Powered by
This message was deleted.
# ask-for-help
s
This message was deleted.
b
@Xipeng Guan do I need to specially disable MinIO?
When I do a 
bentoml push
I think it's still going to MinIO and not to GCS, or at least I expect something to fail if I configured something wrongly
x
@Benjamin Tan you can change the S3 configuration of yatai helm release
b
yeah that's what I did
I checked that the envvars were updated too
So when I did 
bentoml push
I expected it to go to GCS or blow up but not MinIO
rollout restarted too
x
then restart the yatai deployment
b
I'll try again later 🙂
x
Copy code
kubectl -n yatai-system rollout restart deploy/yatai
you can check the s3 configuration by:
Copy code
helm get values yatai -n yatai-system
and
Copy code
kubectl -n yatai-system exec -it deploy/yatai -- env | grep -i s3
👍 1
b
Hmm so I tried this and I can see that the envvars have been updated
But there's still nothing in GCS
So something more interesting. I've deleted all the MinIO pods and I'm still able to push and yet the bucket is still empty 😛
x
I'm suspecting that the yatai you pushed to and the yatai you checked are not the same yatai
Copy code
cat ~/bentoml/.yatai.yaml
b
Hmm using the same token
I can see the tag in the Yatai UI
I've noticed something similiar where my MinIO was misconfigured, and bentoml push still works but then I get no error and the Bento isn't in MinIO
Actuuuuuuuuuuuuuualllly
Do you think it would work if there's a MinIO gateway?
yatai <---> MinIO Gateway <---> GCS
Oh I tried another way. I've added a Lifecycle Rule via the MinIO console and added GCS Cloud Storage as a tier
Open in Slack
PreviousNext
Powered by