-
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
Yatai customize DNS domain for internal components #265
Comments
@mts-dyt Thanks for the feedback! The default minio component is intended to be used in a test environment, you can specify external S3 during installation so that minio will not be installed. It is designed to work out of the box, and we automatically generate the domain name and certificate to save users valuable time from having to manually configure it themselves. If you really want to use our minio installation, you can do so by modifying the yatai-minio ingress resource under the yatai-components namespace, but of course, yatai will remove the logic to automatically install minio and docker-registry later |
@yetone , when customizing the Yatai ingress with my own domain without SSL, the bento push command still refers to https:
update: This is fixed in |
I finally managed to install a MinIO gateway to Azure Blob Storage.
Helm custom values should look like:
On my side, this issue can be closed as the new nginx annotation is available: |
Hello bentoml team 👋
My goal is to have a production ready BentoML platform on AZURE, I managed to have these features working:
I still have one painful point concerning the storage.
For AZURE, I can't find a suitable option for storing data outside of the cluster (MinIO gateway for blob storage is end of support: https://blog.min.io/deprecation-of-the-minio-gateway/).
If I used the default MinIO installation there are settings which are incompatible with our security policies:
yatai-components
is installed and exposed on URL like*.apps.yatai.dev
Even if I customize the NGINX setting after the installation, there are still some reference to the old URL MinIO (when we push local bento to Yatai) that lead to error.
Is it possible to customize the domain name (through an env vars for example) for NGINX exposition of internal components and add custom annotation in NGINX exposition?
The text was updated successfully, but these errors were encountered: