-
Notifications
You must be signed in to change notification settings - Fork 209
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
[Backport for v2.7] 763 document aws out of tree v2prov #1080
[Backport for v2.7] 763 document aws out of tree v2prov #1080
Conversation
…and 1025 refresh created/updated relevant docs pages, moved vsphere migration guide to new migration section
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.
Since 1.27 isn't available for all of 2.7.x, we need to include something like _Available as of vX.Y.Z_
on the pages/sections that are specific to 1.27.
Add mention of Rancher Prime to the pages to let users know that 1.27 support is specific to v2.7.11, which is Prime |
@snasovich @CamrynCarter @btat @gunamata this is mostly a backport of the docs for 2.8, however I am also adding the following note at the top of two relevant v2.7 files, concerning migration from in-tree to out-of-tree cloud providers:
What do you think? |
FYI, @gunamata said it's ok when I showed it to him. |
LGTM, thanks @btat. |
...guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/amazon.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Billy Tat <[email protected]>
Related to #763, #844 and #1025
Reminders
See the README for more details on how to work with the Rancher docs.
Verify if changes pertain to other versions of Rancher. If they do, finalize the edits on one version of the page, then apply the edits to the other versions.
If the pull request is dependent on an upcoming release, make sure to target the release branch instead of
main
.Description
From Slack:
Comments
The updates to the migrations guides occurred across 2 PRs, so I was combing through both. I think this covered everything for v2.7
This is for whichever upcoming v2.7 release adds support for Kubernetes 1.27. As noted by Billy below, when we know for sure, we need to add we need something like Available as of vX.Y.Z on the pages/sections that are specific to 1.27.