-
Notifications
You must be signed in to change notification settings - Fork 73
Add known issue for Fleet UI upgrade option #1753
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
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
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.
Thanks a ton!
(cherry picked from commit c89853a)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit c89853a) # Conflicts: # docs/en/ingest-management/release-notes/release-notes-8.18.asciidoc
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
This adds the following known issue content below to the 8.18.0, 7.17.4 and 7.17.3 release notes. Kyle, I kept the wording pretty much as you proposed. Thanks for the nice and clear issue!
Closes: #1749