Update "Upgrade Elastic Cloud Enterprise" doc and add known issue link as reference #4402
+5
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
[1]
One thing during I was working on ECE known issue documentation with @rseldner and @hubbleview, we got a common agreement that we should add the link of our ECE known issue into ECE upgrade doc, so that user could have smoother upgrade experience. (There are some popular known issues outstandingly exist in upgrading path to 3.8 and 4)
I wrote up this quick one to achieve the goal.
Internal reference: link
[2]
There are some other cosmetic changes, mainly make the items described in requirements section to aligned in its format: The short piece with bold font.
Generative AI disclosure
Preview / View
Before merge
deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md
After merge
https://www.elastic.co/docs/deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise