Skip to content
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

Conversation

martyav
Copy link
Contributor

@martyav martyav commented Jan 22, 2024

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:

Hi, With regards to one of the upcoming rancher releases where k8s 1.27 supported will be added to rancher 2.7 line, there are these docs updates that need to be backported to the 2.7 docs. The 844 needs to be backported to 2.7 version. It looks like the second PR was already applied to the past rancher versions (2.7, 2.6..) so I guess we don't have to do anything for the 1025. [...] As you worked on the PRs, Can you please take of backporting #844 to 2.7? Thanks.

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.

…and 1025 refresh

created/updated relevant docs pages, moved vsphere migration guide to new migration section
@martyav martyav added this to the v2.7.next milestone Jan 22, 2024
@btat btat modified the milestones: v2.7.next, v2.7.11 Jan 22, 2024
Copy link
Contributor

@btat btat left a 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.

@martyav martyav changed the base branch from main to release/v2.7.11 January 26, 2024 18:39
@martyav
Copy link
Contributor Author

martyav commented Feb 7, 2024

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

@martyav
Copy link
Contributor Author

martyav commented Feb 7, 2024

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

:::note
Rancher Prime provides access to Rancher v2.7.11, a version of Rancher v2.7.x which has support for Kubernetes 1.27. If you use Rancher v2.7.11 and upgrade to Kubernetes 1.27, you must use an out-of-tree cloud provider.
:::

What do you think?

@martyav martyav added MERGE ON RELEASE Don't merge until the moment the next release publishes and removed DO NOT MERGE labels Feb 12, 2024
@btat
Copy link
Contributor

btat commented Feb 16, 2024

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

:::note
Rancher Prime provides access to Rancher v2.7.11, a version of Rancher v2.7.x which has support for Kubernetes 1.27. If you use Rancher v2.7.11 and upgrade to Kubernetes 1.27, you must use an out-of-tree cloud provider.
:::

What do you think?

FYI, @gunamata said it's ok when I showed it to him.

@CamrynCarter
Copy link

LGTM, thanks @btat.

@martyav martyav requested a review from btat February 20, 2024 19:22
@martyav martyav requested a review from btat February 20, 2024 20:29
@sunilarjun sunilarjun merged commit 7383ce7 into rancher:release/v2.7.11 Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MERGE ON RELEASE Don't merge until the moment the next release publishes next-release This PR is tied to the next Rancher release and should take higher priority
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants