-
Notifications
You must be signed in to change notification settings - Fork 108
Updates Upgrade ECK page #702
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
We cannot assume the content of this document is valid, as we don't know the details about how to upgrade to 3.x. Actually with the implemented changes (replacing occurrences of 2.16 with 3.0) the content is probably incorrect, as what was a minor upgrade in the past (2.0 towards 2.x) is now a major upgrade and we are stating:
We don't know if the previous is valid (might be, but might not be). I think we need to either involve devs here to help with the upgrade to 3.0 process or just merge this document and devs will refine at a later stage. @pebrc , @barkbay , what do you think? This PR just adds the ECK upgrade document migrated to markdown to the new Information Architecture (IA): https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/702/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s We have applied very small changes replacing 2.16 with 3.0.0. Let us know how you would like to handle this. |
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.
Everything looks good in terms of structure and format.
I just raised a comment about a sentence to improve.
after merging we need to let ECK devs know that the upgrade to 3.0.0 doc is this one. They will probably need to update the content.
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
There are no major technical changes in version 3.0, so I think the upgrade documentation can remain unchanged.
Thanks @barkbay , then we can merge it and refine at a later stage if needed. |
### [Preview](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/702/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s) This PR updates the Upgrade Elastic Cloud on Kubernetes page. Related issue: https://github.com/elastic/docs-projects/issues/460 --------- Co-authored-by: Janeen Mikell Roberts <[email protected]>
Preview
This PR updates the Upgrade Elastic Cloud on Kubernetes page.
Related issue: https://github.com/elastic/docs-projects/issues/460