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
Is this a new feature, an improvement, or a change to existing functionality?
Change
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
To this point, the Kubernetes Helm charts for Morpheus have been managed internally by NVIDIA. The chart versions are updated to coincide with each Morpheus GitHub and NGC release, and the charts are published to NGC post-release. However, from since the early days of the project to now, the basic form and function of the charts have changed little. This means that from release to release the only change is really the version of the Morpheus and MLflow container images. Now there are workflow use case charts that also are published with variations from the classic charts for microservices like postfix, roundcube, postgresql, etc.
Describe your ideal solution
amalgamate the basic charts along with the workflow use case charts into an uber chart
the templates would be brought together in one repo (somewhere in GH nv-morpheus)
new Helm use case deployments would be added to this repo
provide separate Helm values files for configuring the various deployment use cases
add a "latest" tag with each Morpheus NGC image release which will be referenced by the new uber chart
switch from CalVer to SemVer for the chart versions to underscore the lifecycle decoupling
change default ImagePullPolicy to "Always"
update Cloud Native deployment docs appropriately
Additional context
Unresolved:
whether to continue to rely on cnpack or not for some dependent microservices
if the Triton project included their deploy directory in their NGC image then it would not be necessary for Morpheus to publish the plugin image, but CVE remediation would be pushed to the Triton project
Code of Conduct
I agree to follow this project's Code of Conduct
I have searched the open feature requests and have found no duplicates for this feature request
The text was updated successfully, but these errors were encountered:
Is this a new feature, an improvement, or a change to existing functionality?
Change
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
To this point, the Kubernetes Helm charts for Morpheus have been managed internally by NVIDIA. The chart versions are updated to coincide with each Morpheus GitHub and NGC release, and the charts are published to NGC post-release. However, from since the early days of the project to now, the basic form and function of the charts have changed little. This means that from release to release the only change is really the version of the Morpheus and MLflow container images. Now there are workflow use case charts that also are published with variations from the classic charts for microservices like postfix, roundcube, postgresql, etc.
Describe your ideal solution
Additional context
Unresolved:
deploy
directory in their NGC image then it would not be necessary for Morpheus to publish the plugin image, but CVE remediation would be pushed to the Triton projectCode of Conduct
The text was updated successfully, but these errors were encountered: