Skip to content

Conversation

pebrc
Copy link
Contributor

@pebrc pebrc commented Aug 20, 2025

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.

Copy link

github-actions bot commented Aug 20, 2025

🔍 Preview links for changed docs

@kilfoyle
Copy link
Contributor

@pebrc I think there are two options:

Using a code callout:

(three backticks)
1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1 <1>
(three backticks)

1. The restart happens only if you're using the stack monitoring feature in ECK.

Which renders like this:

code

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:

(three backticks)
1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1
(three backticks)
::::{admonition} Notes
Note the following about rolling restarts:
- The restart only happens if the user is making use of the stack monitoring feature in ECK. 
- Stepping over one of these versions, for example, upgrading ECK from 2.6 to 2.9, still triggers a rolling restart.
::::

which renders like this:

notes

@pebrc
Copy link
Contributor Author

pebrc commented Aug 20, 2025

@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.

@kilfoyle
Copy link
Contributor

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: 1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1, 3.2, 3.3, 3.4 <1>
this doesn't work: 1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1 <1>, 3.2, 3.3, 3.4

So, it would be important to include the version explicitly in the text.

Copy link
Contributor

@kilfoyle kilfoyle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚀

@pebrc pebrc enabled auto-merge (squash) August 21, 2025 13:38
@pebrc pebrc merged commit fe64369 into elastic:main Aug 21, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants