-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Bug 1281651, added sizing guidelines for etcd service nodes #3448
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
Bug 1281651, added sizing guidelines for etcd service nodes #3448
Conversation
lgtm, but ideally I'd like @sferich888 to once over as well. |
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.
LGTM
a|* Minimum 20 GB hard disk space for etcd data. | ||
* Consult | ||
link:https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#hardware-recommendations[Hardware | ||
Recommendations] to properly size your etcd nodes. |
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.
The information in this link is great, however I don't think it looks good for us to point customers at github wiki page to define such an important concept.
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.
@timothysc thoughts?
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.
@timothysc Please see this comment from @sferich888 . How should we move forward? Thanks!
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.
I don't thinks it's a concern at this time. My 0th concern is getting the information in the hands of those who need it, and it staying current, and this is the easiest way to do that.
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.
I'm going to merge what we have. We can continue to iterate on this as it evolves.
[rev_history] |
https://bugzilla.redhat.com/show_bug.cgi?id=1281651
Also closes #3447