Skip to content

Fabric: exact instance configuration details in cluster creation documentation #488

Description

@pbrumblay

Issue Type

Incorrect information

Content Location

https://github.com/HarperFast/documentation/blob/main/fabric/cluster-creation-management.md

What's wrong?

This page:

https://github.com/HarperFast/documentation/blob/main/fabric/cluster-creation-management.md

Should define exact performance metrics for "Free, Medium, High, Very High". - or provide a link to this information.

I believe them to be...

  • Free: 5 GB storage, 1 core, 2 threads, 1 GB memory
  • Medium: 10 GB storage, 1 core, 2 threads, 2 GB memory
  • High: 20 GB storage, 4 cores, 8 threads, 4 GB memory

But I'm not entirely certain.

Suggested improvement

No response

Additional context

No response

Are you planning to fix this issue?

No, just reporting the issue

First-time contributor support

  • I'm new to contributing and would appreciate guidance on the process
  • I'd like help understanding the project structure
  • I need assistance with setting up the development environment
  • I'm comfortable contributing but new to this project specifically

Activity

  1. added
    content📝 Content specific issues and requests - text, examples, missing info, or clarity
    on May 7, 2026
  2. stephengoldberg commented on May 7, 2026

    @stephengoldberg
    Contributor

    @pbrumblay can you explain why this is labeled as a bug?

  3. pbrumblay commented on May 7, 2026

    @pbrumblay
    Author

    I selected the "content issue" issue type.

    It looks like Harper's documentation template has the "bug" label in it by default: https://github.com/HarperFast/documentation/blob/main/.github/ISSUE_TEMPLATE/content-issue.yml?plain=1#L3

  4. pbrumblay commented on May 7, 2026

    @pbrumblay
    Author

    Note: I personally don't consider it a documentation "bug". It's not incorrect information but I believe the content could be improved with this information.

  5. pbrumblay commented on May 7, 2026

    @pbrumblay
    Author

    I don't have "triage" access to this repo so I can't manage the labels.

  6. BboyAkers commented on May 7, 2026

    @BboyAkers
    Contributor

    I'll look into fleshing this page out more! 🙂

  7. stephengoldberg commented on May 7, 2026

    @stephengoldberg
    Contributor

    @pbrumblay thank you this is super helpful and explains a lot of confusion on my end.

  8. pbrumblay commented on May 7, 2026

    @pbrumblay
    Author

    Looks like "Content Request" is maybe a better issue type for this in the future. It has "content" and "enhancement" labels. I'll make sure to be more careful on issue selection.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    content📝 Content specific issues and requests - text, examples, missing info, or clarity

    Type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions