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.

Sign up for GitHub

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

Jump to bottom

Add documentation how to configure BMO for single namespace #1261

Open
tuminoid opened this issue Apr 26, 2023 · 13 comments · May be fixed by #1867
Open

Add documentation how to configure BMO for single namespace #1261

tuminoid opened this issue Apr 26, 2023 · 13 comments · May be fixed by #1867
Assignees
@Sunnatillo @NymanRobin
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

tuminoid commented Apr 26, 2023 •
edited
Loading

User Story

As a operator I would like to have documentation how to configure BMO for single namespace operation so it wouldn't need wide access to cluster-wide secrets.

Detailed Description

I would like to have documentation how to configure BMO for single namespace operation. This would improve BMO security posture by limiting its access to Secrets that doesn't belong to it.

Anything else you would like to add:

Originated from: #1241

/kind documentation

edit: also needs Manifest changes to facilitate Roles and RoleBindings instead of Cluster equivalents.
@metal3-io-bot metal3-io-bot added kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Apr 26, 2023
@tuminoid
Copy link
Member Author

/assign @zaneb

@Rozzii
Copy link
Member

Rozzii commented Apr 26, 2023

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Apr 26, 2023
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 25, 2023
@Rozzii
Copy link
Member

Rozzii commented Aug 2, 2023

Would be welcomed I will move this to frozen, no need to always remove the stale
/lifecycle frozen

@metal3-io-bot metal3-io-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 2, 2023
@Rozzii Rozzii added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Aug 2, 2023
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 31, 2023
@Rozzii
Copy link
Member

Rozzii commented Nov 1, 2023

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 1, 2023
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 30, 2024
@tuminoid
Copy link
Member Author

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 30, 2024
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2024
@tuminoid
Copy link
Member Author

tuminoid commented May 6, 2024

/remove-lifecycle stale
/lifecycle frozen

@metal3-io-bot metal3-io-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 6, 2024
@tuminoid
Copy link
Member Author

tuminoid commented May 6, 2024

/unassign
I don't think Zane is working on this, freeing it up.

@NymanRobin
Copy link
Member

/assign

@NymanRobin NymanRobin linked a pull request Aug 9, 2024 that will close this issue
Open
7 tasks
@tuminoid
Copy link
Member Author

/assign @Sunnatillo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Sunnatillo Sunnatillo

@NymanRobin NymanRobin

Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Metal3 - Roadmap
Status: Backlog
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

draft: add namespace scoped operator mode Nordix/baremetal-operator
6 participants
@zaneb @tuminoid @Rozzii @Sunnatillo @NymanRobin @metal3-io-bot