-
Notifications
You must be signed in to change notification settings - Fork 159
Note that upgrades to ECK 3.1 cause a restart #2634
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
Conversation
🔍 Preview links for changed docs |
@pebrc I think there are two options: Using a code callout:
Which renders like this: ![]() One problem is that the admonition must appear at the end of the line. Alternatively, we could update the admonition that appears below the versions list:
which renders like this: ![]() |
@kilfoyle thanks for the suggestions. I think the problem is that is not clear to the reader which version it applies to. Especially in the second version (which implies it applies to all version and that would be wrong). I think I am going with the callout and mention the version explicitly again in the text. |
I think that's a good approach. Note that the callout has to appear at the end of the line: this works: So, it would be important to include the version explicitly in the text. |
Co-authored-by: David Kilfoyle <[email protected]>
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! 🚀
I would like to add a note that the restart only happens if the user is make use of the stack monitoring feature in ECK but I don't know the best way to express that in the docs syntax.
Normally I would have wanted to add a footnote but I don't think we have those in the docs/markdown. Open for suggestions. If there is no good way that an unqualified mention is still better than the status quo.