-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[bitnami/mlflow] MLFLOW_S3_ENDPOINT_URL not inject if i dont want to use minio #26397
Comments
Hi, I believe that the condition should be like this Instead of
it should be
As you spotted the issue. Would you like to submit a PR fixing it? |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
@andresbono please kindly reopen. There is a PR open for this. |
Name and Version
mlflow/1.2.0
What architecture are you using?
None
What steps will reproduce the bug?
it was working fine before and today I am upgrading my mlflow to the latest mlfow 2.13.0.
In my values.yaml
I need to set minio to false due to company policy.
But I have my custom s3 host, e.g my company provided s3-compatible host:
In this PR , it introduced that i must enable minio otherwise my custom value won't able to inject.
I have to temporary remove the PR introduced condition.
Are you using any custom parameters or values?
No response
What is the expected behavior?
No response
What do you see instead?
NA.
Additional information
No response
The text was updated successfully, but these errors were encountered: