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
One of the points open in our list of TODOs to make this project usable in pŕoduction is the hosting of the Harmony chart. Currently, to install this chart correctly, we need to clone the whole openedx-k8s-harmony repository and use Helm to install it from the source code. Additionally, we need to push the artifacts of the dependency charts to prevent running extra commands when installing the main chart. This is not ideal from an operator's perspective.
We should stick to the standard and host the chart in a Helm repository to make its installation more intuitive:
There's a tool called chart-releaser that helps to add Helm chart artifacts to GitHub Releases and host such releases in GitHub pages. To automate the process, the chart-releaser-action can be included in the repo workflow to create new releases of the chart and update properly the GitHub Pages hosting. The prerequisites to use the action are included here.
This releaser is used by most of the well-known Helm charts (ingress-nginx, prometheus-charts, among others) to handle the releases and the hosting. However, the discussion is open to bring other options to the table.
The text was updated successfully, but these errors were encountered:
Guys, I stepped up and created a PR to implement the release and hosting mechanisms of the harmony chart using chart-releaser. Feel free to check it out and provide feedback :)
One of the points open in our list of TODOs to make this project usable in pŕoduction is the hosting of the Harmony chart. Currently, to install this chart correctly, we need to clone the whole openedx-k8s-harmony repository and use Helm to install it from the source code. Additionally, we need to push the artifacts of the dependency charts to prevent running extra commands when installing the main chart. This is not ideal from an operator's perspective.
We should stick to the standard and host the chart in a Helm repository to make its installation more intuitive:
There's a tool called chart-releaser that helps to add Helm chart artifacts to GitHub Releases and host such releases in GitHub pages. To automate the process, the chart-releaser-action can be included in the repo workflow to create new releases of the chart and update properly the GitHub Pages hosting. The prerequisites to use the action are included here.
This releaser is used by most of the well-known Helm charts (ingress-nginx, prometheus-charts, among others) to handle the releases and the hosting. However, the discussion is open to bring other options to the table.
The text was updated successfully, but these errors were encountered: