-
Notifications
You must be signed in to change notification settings - Fork 69
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
Restructure hardware requirements table #559
Restructure hardware requirements table #559
Conversation
✅ Deploy Preview for harvester-preview ready!
|
@bk201 I have updated the file. Please confirm that I can ignore the following items on the Support Matrix page.
|
@jillian-maroket Sorry for the delay. These sentences are important because we use a SLES derivative and don't support software RAID yet. |
@bk201 Thank you for your comment. I updated the doc to include information from the Support Matrix page, but changed the YES Certification link because the original one is broken. PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
This comment made me realize that the doc does not clearly distinguish between requirements and recommendations. Users typically want to know if the system can run on their existing hardware. This can prompt them to search for terms such as requirements/required and recommendations/recommended.
I understand that the team is more comfortable with testing/development vs. production. Because of this, I updated the existing hardware requirements table to make the distinction clearer. Markdown doesn't allow merging of table cells so some information is repeated.
Question: Do we want to add the following details that are mentioned here?