diff --git a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/unified-payg-faq.md b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/cloud-marketplace-payg-integration.md similarity index 94% rename from versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/unified-payg-faq.md rename to versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/cloud-marketplace-payg-integration.md index 876b540d61b..d9aeb42b323 100644 --- a/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/unified-payg-faq.md +++ b/versioned_docs/version-2.7/integrations-in-rancher/cloud-marketplace/cloud-marketplace-payg-integration.md @@ -79,7 +79,7 @@ While it is not possible to transact/bill Rancher Prime in China, it is possible #### Can I still deploy Rancher using the "Rancher Setup" listing from the AWS Marketplace? -"Rancher Setup" is no longer available via AWS Marketplace. Customers should deploy an EKS Cluster to host Rancher. Follow the steps in this [guide](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks.md) except for the Rancher installation. The Rancher product installation should be carried out as per [installing the Rancher Prime PAYG offering on Amazon's AWS Marketplace](../integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/installing-rancher-prime.md). +"Rancher Setup" is no longer available via AWS Marketplace. Customers should deploy an EKS Cluster to host Rancher. Follow the steps in this [guide](../../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks.md) except for the Rancher installation. The Rancher product installation should be carried out as per [installing the Rancher Prime PAYG offering on Amazon's AWS Marketplace](../cloud-marketplace/aws-marketplace-payg-integration/installing-rancher-prime.md). ### Billing @@ -125,7 +125,7 @@ Rancher Prime has different pricing tiers when purchasing via the AWS and Azure If using the Rancher Prime listing in the cloud provider marketplace, billing will commence from the time of deployment. -Rancher can be deployed manually using the standard documentation and repositories. When ready to benefit from a supported platform and have this billed via the marketplace, follow the available [documentation](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md) to deploy Rancher Prime from the marketplace and migrate. +Rancher can be deployed manually using the standard documentation and repositories. When ready to benefit from a supported platform and have this billed via the marketplace, follow the available [documentation](../../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md) to deploy Rancher Prime from the marketplace and migrate. #### How does SUSE calculate the ‘average number of managed nodes’ to bill for? @@ -222,7 +222,7 @@ Yes. The billing mechanism of each deployment is independent, each product will In order to benefit from monthly billing via the Marketplace, the primary Rancher cluster needs to be deployed from the listing, it is then possible to migrate the existing Rancher configuration to the new deployment. -Please follow the [documentation](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md) and be sure to back up the existing Rancher configuration. +Please follow the [documentation](../../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md) and be sure to back up the existing Rancher configuration. ### Technical (Product) @@ -230,7 +230,7 @@ Please follow the [documentation](../getting-started/installation-and-upgrade/in It is very simple to [open a support case](https://scc.suse.com/cloudsupport) with SUSE for Rancher Prime. Create a ‘supportconfig’ via the Rancher UI and upload the output to the SUSE Customer Center. The support config bundle can be exported from the Rancher console using the ‘Get Support’ button at the bottom of the page. For deployments when Rancher is managing multiple downstream clusters, export the support config bundle from the primary cluster only. -If the billing mechanism on the primary cluster is active, a support case will be opened. Further details can be found in the [documentation](../integrations-in-rancher/cloud-marketplace/supportconfig.md). +If the billing mechanism on the primary cluster is active, a support case will be opened. Further details can be found in the [documentation](../cloud-marketplace/supportconfig.md). #### What are the resource requirements for installing Rancher on AKS or EKS? @@ -260,4 +260,4 @@ Yes. Managed nodes (managed clusters) can run anywhere. SUSE Rancher will count #### How do I get fixes and updates for Rancher? -To update to the latest version of the Rancher Prime PAYG offering supported in the marketplace listing, please see [upgrading Rancher Prime PAYG cluster in AWS](../integrations-in-rancher/cloud-marketplace/aws-marketplace-payg-integration/upgrading-rancher-payg-cluster.md). +To update to the latest version of the Rancher Prime PAYG offering supported in the marketplace listing, please see [upgrading Rancher Prime PAYG cluster in AWS](../cloud-marketplace/aws-marketplace-payg-integration/upgrading-rancher-payg-cluster.md). diff --git a/versioned_sidebars/version-2.7-sidebars.json b/versioned_sidebars/version-2.7-sidebars.json index 504f8d0ee07..72170609dbe 100644 --- a/versioned_sidebars/version-2.7-sidebars.json +++ b/versioned_sidebars/version-2.7-sidebars.json @@ -1117,7 +1117,7 @@ "label": "Cloud Marketplace Pay-as-you-go (PAYG) Integration", "link": { "type": "doc", - "id": "integrations-in-rancher/cloud-marketplace/unified-payg-faq" + "id": "integrations-in-rancher/cloud-marketplace/cloud-marketplace-payg-integration" }, "items": [ {