Why don't we have a Chart Package?
matthewei opened this issue · 7 comments
User Story
As a user I would like to have a high level description for reasons
we want to have a chart package to install BMO. we can define the values.yaml to controller how to install the BMO
/kind feature
This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Helm has no support for CRD upgrades, so this will anyway need to be handled separately. So why have two tools when kustomize can cover it all?
Then there is the question of config files. For BMO it is not so bad, just a few environment variables are needed and they can be easily added through helm values. But for something more complex, like Ironic, you quickly end up with inline config in the helm values. 😬
I'm not completely objecting having a helm chart though. If someone is willing to create one and do a PR to add it, go for it!
yeah, Thanks a lot for your timely reply.The user can learn how to set variables for the BMO and Ironic if we provied the helm chart. From my point of view, using "export variables" may not be a good method.
if we don't want to use helm chart. I think we can genereate deploying-scripts for user. The users don't need to clone code from github to execute './tools/deploy.sh ------'.
If we want more people to use metal3, we should provide a more convenient installation method. what about you?
I totally agree! Have you seen the new quick-start? My goal was to address exactly these issues. The user does not need to have go installed or the repo cloned or run random scripts from the internet. They still need to provide some configuration and credentials though. I understand that kustomize isn't as well known as helm and the initial deployment does take more time, but I do think this is a great improvement over the deploy.sh script and should work well in most cases.
yes, I have read it and followed it. But I foud as a fresh man I need more time to study it. The official documentation does not match the actual situation. I can't deploy a cluster according to the documentation.
This was discussed a few times within the community, but until helm has native CRD registration support everything that we would create would end up looking like a hack. Sadly at the moment we can't deliver a nice Helm chart as part of the releases but maybe in the future. So I will close this ticket as the original question was answered by @lentzi90 .