[
https://issues.apache.org/jira/browse/YUNIKORN-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104466#comment-17104466
]
Kinga Marton edited comment on YUNIKORN-140 at 5/11/20, 1:39 PM:
-----------------------------------------------------------------
[~wwei], I checked [https://github.com/helm/charts]. That seems to be a good
solution as well, but for the long term supportability wouldn't be better to
use our own repo for this purpose? This way in case of any changes in the helm
chart we will not depend on other team and we can publish our changes more
quickly.
was (Author: kmarton):
[~wwei], I checked [https://github.com/helm/charts]. That seems to be a good
solution as well, but for the long term supportability wouldn't be better to
use our own repo for this purpose? This way in case of any changes in the helm
chart we will not depend on other team and we can publish our changes quicker.
> Create helm chart repository and publish it to helmhub
> ------------------------------------------------------
>
> Key: YUNIKORN-140
> URL: https://issues.apache.org/jira/browse/YUNIKORN-140
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Kinga Marton
> Assignee: Kinga Marton
> Priority: Major
>
> Create a helm chart repository and publish the charts to
> [https://hub.helm.sh/.|https://hub.helm.sh/] This will further help user to
> try yunikorn out easily.
> How to create the helm chart repository is described here:
> [https://helm.sh/docs/topics/chart_repository/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
