-
Notifications
You must be signed in to change notification settings - Fork 246
Update Sidecar requirements documentation. #1100
Conversation
Just to clarify: And I'm not suggesting we should document any of that ;-) |
@mpfz0r Thanks for the clarification! |
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.
Looks good. I guess we should also apply that change to the older doc branches. like at least 3.3 and 3.2.
Right. I'll take care of that, too. |
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.
+1. Thank you, @juju2112
* Update sidecar requirements to reflect Graylog2/collector-sidecar#391. * Fix sidecar version in requirements matrix. * Update versions in matrix for clarity. (cherry picked from commit 5045588)
* Update sidecar requirements to reflect Graylog2/collector-sidecar#391. * Fix sidecar version in requirements matrix. * Update versions in matrix for clarity. (cherry picked from commit 5045588)
* Update sidecar requirements to reflect Graylog2/collector-sidecar#391. * Fix sidecar version in requirements matrix. * Update versions in matrix for clarity. (cherry picked from commit 5045588)
* Update sidecar requirements to reflect Graylog2/collector-sidecar#391. * Fix sidecar version in requirements matrix. * Update versions in matrix for clarity. (cherry picked from commit 5045588)
I have not released Graylog Sidecar
1.1.0
yet, but when I do, I'd like the documentation to be clear on the new server requirements (See Graylog2/collector-sidecar#391).This should not be merged yet (not until Sidecar
1.1.0
is released). But I would like feedback on how clear this looks. Does it make sense?I think the idea is that if Sidecar installs Beats 7.0, that older versions of Graylog won't work with it.