Skip to content

Create up to date CR reference images #501

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
Open
tuminoid opened this issue Jan 21, 2025 · 5 comments
Open

Create up to date CR reference images #501

tuminoid opened this issue Jan 21, 2025 · 5 comments
Labels
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

Create up to date CR reference images. In #499, very old (5y+) images and crs_reference.md is removed, but we liked the graphics showing the relations.

This would optimally be something that can be part of the Metal3 book, perhaps in Developer section, and perhaps something more maintainable, like Mermaid graphs (ie. Markdown).
@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Jan 21, 2025
@tuminoid tuminoid mentioned this issue Jan 21, 2025
Merged
@tuminoid
Copy link
Member Author

/kind documentation

@metal3-io-bot metal3-io-bot added the kind/documentation Categorizes issue or PR as related to documentation. label Jan 21, 2025
@Rozzii
Copy link
Member

Rozzii commented Jan 29, 2025

/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 Jan 29, 2025
@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, 2025
@Rozzii
Copy link
Member

Rozzii commented May 9, 2025

/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 May 9, 2025
@Rozzii
Copy link
Member

Rozzii commented May 9, 2025

/lifecycle frozen

@metal3-io-bot metal3-io-bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tuminoid @Rozzii @metal3-io-bot