Add PAYG instructions to v2.8

[LucasSaintarbor]

Fixes #[issue_number]

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, remember to add a "MERGE ON RELEASE" label and set the proper milestone.

Description

Comments

[LucasSaintarbor]

@jeremy-moffitt Referring to #1354, should we recommend users be on Rancher v2.8.4? Should the v2.7 docs be kept or removed? (https://ranchermanager.docs.rancher.com/v2.7/integrations-in-rancher/cloud-marketplace/cloud-marketplace-payg-integration)

[jeremy-moffitt]

Regarding 2.7 support, any existing customers running PAYG on 2.7 are still in support and do not have to migrate, so I'm hesitant to remove the 2.7 docs at this point. We could add a note indicating the listings have been updated to 2.8.4 and customers are encouraged to remain current with the listing to get the latest features and security fixes.

@jeremy-moffitt Referring to #1354, should we recommend users be on Rancher v2.8.4? Should the v2.7 docs be kept or removed? (https://ranchermanager.docs.rancher.com/v2.7/integrations-in-rancher/cloud-marketplace/cloud-marketplace-payg-integration)

[jeremy-moffitt]

@LucasSaintarbor anything you need from me or my team on this? We'll be starting the updates to 2.9.1 in a couple weeks so we'll have a new request... for now the 2.8.4 info is current.

[LucasSaintarbor]

@LucasSaintarbor anything you need from me or my team on this? We'll be starting the updates to 2.9.1 in a couple weeks so we'll have a new request... for now the 2.8.4 info is current.

Hey @jeremy-moffitt, sorry for the late reply. May you review my latest update (393aac0)?

[jeremy-moffitt]

Content changes look good to me. The verbiage around versions is clear and makes sense. Thanks for making the update!

[jeremy-moffitt]

Please let me know if I need to track down another reviewer from my team. I'm assuming one of the doc writers will perform a review aimed at catching non-content issues. Thanks.

[martyav]

I just looked at the new Supported Versions blurb as I'm trusting (for now) that the v2.8 pages are a straight copy-paste of v2.7 and have already been reviewed in previous PRs. I edited the new section for brevity and put the v2.8 rec more forward, so it's clear to users what version they should use