Skip to content
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

Open
ish-xyz opened this issue Oct 10, 2024 · 7 comments
Open

The installation of the BMO is painful #1987

ish-xyz opened this issue Oct 10, 2024 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@ish-xyz
Copy link

ish-xyz commented Oct 10, 2024

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

@metal3-io-bot metal3-io-bot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Oct 10, 2024
@metal3-io-bot
Copy link
Contributor

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-sigs/prow repository.

@ish-xyz
Copy link
Author

ish-xyz commented Oct 10, 2024

cc: @dhellmann

@dhellmann
Copy link
Member

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.

@ish-xyz
Copy link
Author

ish-xyz commented Oct 11, 2024

@dhellmann whoops, sorry then!

@mquhuy
Copy link
Member

mquhuy commented Oct 16, 2024

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

@Rozzii
Copy link
Member

Rozzii commented Oct 23, 2024

/triage needs-information

@metal3-io-bot metal3-io-bot added the triage/needs-information Indicates an issue needs more information in order to work on it. label Oct 23, 2024
@Rozzii
Copy link
Member

Rozzii commented Oct 23, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

5 participants