You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mlflow plugin container and helm chart were not deployed to NGC for the last two Morpheus releases.
We need to determine if we should:
Continue support, and deploy these for 24.06 & 24.10.
Discontinue support and update the documentation accordingly.
There are specific issues with both of these.
mlflow-triton plugin:
The code for this plugin was contributed back to the Triton team and now lives in their repo. This creates a weird situation for us, where upon performing a Morpheus release we are building a container with code from another team's repo (and potentially needing to patch/maintain).
helm chart:
This is simply an issue of bandwidth/expertise and the need to stand-up a k8 cluster to deploy/test.
Minimum reproducible example
Relevant log output
Click here to see error details
[Paste the error here, it will be hidden by default]
Full env printout
Click here to see environment details
[Paste the results of print_env.sh here, it will be hidden by default]
Other/Misc.
No response
Code of Conduct
I agree to follow Morpheus' Code of Conduct
I have searched the open bugs and have found no duplicates for this bug report
The text was updated successfully, but these errors were encountered:
Version
24.06, 24.10 & 25.01
Which installation method(s) does this occur on?
Source
Describe the bug.
The mlflow plugin container and helm chart were not deployed to NGC for the last two Morpheus releases.
We need to determine if we should:
There are specific issues with both of these.
mlflow-triton plugin:
helm chart:
Minimum reproducible example
Relevant log output
Click here to see error details
Full env printout
Click here to see environment details
Other/Misc.
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: