-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to run Yatai server in on-premise K8S #252
Comments
Hi @thechaos16! We don't see that case very often, but we've got a particular config that might help:
This will disable the creation of the ingress, which is for people who don't want to expose yatai with an external ip. Not sure all of your environment, but could you try that as a helm option? |
cc @yetone |
@thechaos16 Thanks for your report! Yatai deployment operators always need a load balancer, another solution is not to use the built-in Minio, but to manually specify the s3 configuration. https://github.com/bentoml/Yatai/blob/main/docs/admin-guide.md#aws-s3 |
Thank you for the quick reply. @timliubentoml, I've tried to disable ingress from https://github.com/bentoml/yatai-chart/blob/main/values.yaml#L91, but it still shows the same error. I guess updating helm chart of @yetone, I passed external S3 info by filling https://github.com/bentoml/yatai-chart/blob/main/values.yaml#L50-L58 blocks, but it still fails. Could you let me know if there is another way to not use the built-in Minio? In my K8S dashboard, there are two pods (minio-operator and yatai-minio-console) running. |
@thechaos16 There is an error in the docs that shows setting |
for me this was resolved after i deleted the default postgres pvc.
deleted the whole yatai, yatai postgresql
copied the initial secret and created a new postgresql secret.
i managed to run it with values.yaml.
after i do bentoml push
|
Hello, bentoML team.
I'm recently trying to use bentoML and Yatai on our on-premise K8S cluster, but somehow it failed because we don't have LB service on our cluster. Is there any guide or workarounds to deploy Yatai on non-cloud K8S?
Thank you.
Followings are a few error messages.
The error appears when I tried to push bento to yatai (yatai login is succeeded)
![스크린샷 2022-06-07 오후 3 33 16](https://user-images.githubusercontent.com/16028452/172513950-4519008b-1a0d-45fa-9e9d-4c36e700f6df.png)
And I found that
bentoml push
queries to the pods naemddeployment-yatai-deployment-comp-operator
underyatai-operator
namespace, and it shows following error, and it shows there's noexternalIP
inyatai-ingress-controller-ingress-nginx-controller
The text was updated successfully, but these errors were encountered: