-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The installation of the BMO is painful #1987
Comments
This issue is currently awaiting triage. 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-sigs/prow repository. |
cc: @dhellmann |
Hi, @ish-xyz ! I'm not long actively contributing to metal3, unfortunately. I'm sure one of the maintainers will be interested in your feedback. |
@dhellmann whoops, sorry then! |
Hi @ish-xyz , the community has discussed of adopting helm, but so far we still don't have enough incentives to do so. Would you mind attending our next community meeting and describe your viewpoint and use case there? If the community is persuaded that a helm chart is needed, I'm sure adding it will be easy. Here's information about Metal3 community meeting: https://docs.google.com/document/d/1IkEIh-ffWY3DaNX3aFcAxGbttdEY_symo7WAGmzkWhU/edit?tab=t.0#heading=h.w4ou76o3rp1v |
/triage needs-information |
I have added the needs info label because this is an issue that can only be accepted if the community agrees to it and someone is willing to maintain up to date helm charts. |
User Story
Can you provide a helm chart to install the BMO please?
The getting started guide is not really a guide, and the tool to generate the config requires underlying tools that are not listed anywhere (or at least I couldn't easily find them).
I had to reverse engineer the deployment/getting started process. Which is painful.
Can you just use helm? It is the most common tool to package Kubernetes deployments.
cc: @tuminoid @kashifest
/kind feature
The text was updated successfully, but these errors were encountered: