mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 12:38:05 +00:00
Updated URLS with relative links
This commit is contained in:
LucasSaintarbor
+1
-1
@@ -8,4 +8,4 @@ title: AWS Marketplace Common Issues
|
||||
helm uninstall -n cattle-rancher-csp-deployer-system rancher-cloud
|
||||
```
|
||||
|
||||
1. When migrating Rancher to a different EKS by following the steps specified in [Rancher Backups and Disaster Recovery](https://ranchermanager.docs.rancher.com/pages-for-subheaders/backup-restore-and-disaster-recovery), you must reinstall Rancher Prime on the target EKS cluster after restoring from the backup. Furthermore, the restored Rancher version must not be newer than the version available in the AWS marketplace.
|
||||
1. When migrating Rancher to a different EKS by following the steps specified in [Rancher Backups and Disaster Recovery](/versioned_docs/version-2.7/pages-for-subheaders/backup-restore-and-disaster-recovery.md), you must reinstall Rancher Prime on the target EKS cluster after restoring from the backup. Furthermore, the restored Rancher version must not be newer than the version available in the AWS marketplace.
|
||||
|
||||
+5
-5
@@ -4,11 +4,11 @@ title: Prerequisites
|
||||
|
||||
Before using Rancher Prime on AWS as a pay-as-you-go (PAYG) offering, you need the following resources, information, and tools:
|
||||
|
||||
- A Rancher-compatible EKS cluster. Please see the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) for more details. Please refer to [Creating an EKS cluster](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#creating-an-eks-cluster-for-the-rancher-server) for bringing up an EKS cluster to [install Rancher Prime PAYG](installing-rancher-prime.md).
|
||||
- An ingress is installed on the EKS cluster so that Rancher is accessible outside the cluster. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#5-install-an-ingress) for instructions on deployings Ingress-NGINX on an EKS cluster.
|
||||
- Get the Load Balancer IP. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#6-get-load-balancer-ip) and save the EXTERNAL-IP.
|
||||
- The Rancher hostname must be a fully qualified domain name (FQDN), and its corresponding IP address must be resolvable from a public DNS. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks#7-set-up-dns) for instructions on how to set up DNS. This DNS is set up to point to the EXTERNAL-IP saved.
|
||||
- Installation requires you to have the following tools available and properly configured to access your AWS account and your EKS cluster:
|
||||
- A Rancher-compatible EKS cluster. Please see the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) for more details. Please refer to [Creating an EKS cluster](/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks.md) for bringing up an EKS cluster to [install Rancher Prime PAYG](installing-rancher-prime.md).
|
||||
- An ingress is installed on the EKS cluster so that Rancher is accessible outside the cluster. Please refer to [Rancher documentation](/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks.md#5-install-an-ingress) for instructions on deployings Ingress-NGINX on an EKS cluster.
|
||||
- Get the Load Balancer IP. Please refer to [Rancher documentation](/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks.md#6-get-load-balancer-ip) and save the EXTERNAL-IP.
|
||||
- The Rancher hostname must be a fully qualified domain name (FQDN), and its corresponding IP address must be resolvable from a public DNS. Please refer to [Rancher documentation](/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks.md#7-set-up-dns) for instructions on how to set up DNS. This DNS is set up to point to the EXTERNAL-IP saved.
|
||||
- Installation requires you to have the following tools available and properly configured to access your AWS account, and your EKS cluster:
|
||||
- `aws`
|
||||
- `curl`
|
||||
- `eksctl`
|
||||
|
||||
+1
-1
@@ -2,6 +2,6 @@
|
||||
title: Azure Marketplace Common Issues
|
||||
---
|
||||
|
||||
1. When migrating Rancher to a different AKS cluster by following the steps specified in [Rancher Backups and Disaster Recovery](https://ranchermanager.docs.rancher.com/pages-for-subheaders/backup-restore-and-disaster-recovery), Rancher Prime must be reinstalled via the Azure Marketplace on the target AKS cluster after restoring from the backup. Furthermore, the restored Rancher version must not be newer than the version available in the Azure Marketplace.
|
||||
1. When migrating Rancher to a different AKS cluster by following the steps specified in [Rancher Backups and Disaster Recovery](/versioned_docs/version-2.7/pages-for-subheaders/backup-restore-and-disaster-recovery.md), Rancher Prime must be reinstalled via the Azure Marketplace on the target AKS cluster after restoring from the backup. Furthermore, the restored Rancher version must not be newer than the version available in the Azure Marketplace.
|
||||
|
||||
1. Uninstalling Rancher Prime may not cleanly remove all the resources that were created by Rancher. Users are encouraged to use the [Rancher resource cleanup script](https://github.com/rancher/rancher-cleanup) to perform a more comprehensive cleanup if necessary. However, it is recommended to migrate any other workloads off the cluster and prepare to destroy the cluster to complete the uninstallation since cleanup is not recoverable.
|
||||
|
||||
+3
-3
@@ -4,6 +4,6 @@ title: Prerequisites
|
||||
|
||||
Before using Rancher Prime on Azure as a pay-as-you-go (PAYG) offering, you need the following resources, information, and tools:
|
||||
|
||||
- A Rancher-compatible AKS cluster. Please see the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) for more details. The Rancher Prime PAYG offering can only be installed onto clusters in regions where both the AKS and Azure Container Apps service are available. See the [Azure documentation](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/?products=container-apps,kubernetes-service®ions=all) for details. Please see [Creating an AKS cluster](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks#3-create-the-aks-cluster) for bringing up an AKS cluster to [install Rancher Prime PAYG](installing-rancher-prime.md).
|
||||
- An ingress installed on the AKS cluster so that Rancher is accessible outside of the cluster. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks#5-install-an-ingress) for instructions on how to deploy Ingress-NGINX on AKS cluster.
|
||||
- The Rancher hostname must be a fully qualified domain name (FQDN) and its corresponding IP address must be resolvable from a public DNS. Please refer to [Rancher documentation](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks#7-set-up-dns) for instructions on how to setup DNS.
|
||||
- A Rancher-compatible AKS cluster. Please see the [Rancher support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) for more details. The Rancher Prime PAYG offering can only be installed onto clusters in regions where both the AKS and Azure Container Apps service are available. See the [Azure documentation](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/?products=container-apps,kubernetes-service®ions=all) for details. Please see [Creating an AKS cluster](/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks.md#3-create-the-aks-cluster) for bringing up an AKS cluster to [install Rancher Prime PAYG](installing-rancher-prime.md).
|
||||
- An ingress installed on the AKS cluster so that Rancher is accessible outside of the cluster. Please refer to [Rancher documentation](/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks.md#5-install-an-ingress) for instructions on how to deploy Ingress-NGINX on AKS cluster.
|
||||
- The Rancher hostname must be a fully qualified domain name (FQDN) and its corresponding IP address must be resolvable from a public DNS. Please refer to [Rancher documentation](/versioned_docs/version-2.7/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks.md#7-set-up-dns) for instructions on how to setup DNS.
|
||||
|
||||
@@ -15,7 +15,7 @@ Rancher Prime integrates with the AWS Marketplace as a pay-as-you-go (PAYG) offe
|
||||
|
||||
## Limitations
|
||||
|
||||
- Currently, you must be running Rancher Manager v2.7.9. When you deploy a supported PAYG version, you can update to newer versions of Rancher Manager when the listing is updated.
|
||||
- Currently, you must be running Rancher v2.7.9. When you deploy a supported PAYG version, you can update to newer versions of Rancher when the listing is updated.
|
||||
|
||||
## How to Use
|
||||
|
||||
@@ -65,8 +65,7 @@ Please read the addendum at the end of this FAQ for a list of countries that can
|
||||
|
||||
‘Rancher Setup’ is no longer available via AWS Marketplace. Customers should deploy an EKS Cluster to host Rancher. Please refer to the best practice documentation.
|
||||
|
||||
Follow the steps in the following guide except for the Rancher installation. The Rancher product install should be carried out as per the directions on the Marketplace listing.
|
||||
https://ranchermanager.docs.rancher.com/getting-started/installation-andupgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks
|
||||
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 install should be carried out as per the directions on the Marketplace listing.
|
||||
|
||||
### Billing
|
||||
|
||||
@@ -80,8 +79,7 @@ No. A new deployment of Rancher Prime is required to benefit from the new monthl
|
||||
|
||||
#### I have an existing deployment covered by a Rancher subscription; can I use this new listing in AWS for new deployments?
|
||||
|
||||
Yes, the listing works independently from your existing subscriptions. Please remember that support processes may be different for deployments using
|
||||
your existing subscription and those billed via the AWS Marketplace.
|
||||
Yes, the listing works independently from your existing subscriptions. Please remember that support processes may be different for deployments using your existing subscription and those billed via the AWS Marketplace.
|
||||
|
||||
#### Tell me more about how the billing for Rancher Prime works via AWS?
|
||||
|
||||
@@ -113,9 +111,7 @@ Rancher Prime has different pricing tiers when purchasing via the AWS Marketplac
|
||||
|
||||
If using the Rancher Prime listing in the AWS 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 AWS Marketplace, follow the available documentation to deploy Rancher Prime from the AWS Marketplace and migrate.
|
||||
|
||||
https://ranchermanager.docs.rancher.com/getting-started/installation-andupgrade/install-upgrade-on-a-kubernetes-cluster/upgrades
|
||||
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 AWS Marketplace, follow the available [documentation](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md) to deploy Rancher Prime from the AWS Marketplace and migrate.
|
||||
|
||||
#### How does SUSE calculate the ‘average number of managed nodes’ to bill for?
|
||||
|
||||
@@ -189,9 +185,7 @@ version available at the time of listing.
|
||||
Typically, these are updated quarterly, or more frequently if there are security issues.
|
||||
|
||||
To update Rancher to a current version before the marketplace listing is updated, please
|
||||
see the product documentation.
|
||||
|
||||
https://ranchermanager.docs.rancher.com/pages-for-subheaders/installation-andupgrade
|
||||
see the following [documentation](../pages-for-subheaders/installation-and-upgrade.md).
|
||||
|
||||
#### I have many Kubernetes clusters across multiple AWS accounts, does the Rancher Prime billing still work and enable tiered pricing?
|
||||
|
||||
@@ -217,23 +211,19 @@ Yes, simply deploy the AWS Marketplace listing for Rancher Prime.
|
||||
|
||||
In order to benefit from monthly billing via the AWS 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 and be sure to back up the existing Rancher configuration.
|
||||
|
||||
Documentation can be found at the following link: https://ranchermanager.docs.rancher.com/getting-started/installation-andupgrade/install-upgrade-on-a-kubernetes-cluster/upgrades
|
||||
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)
|
||||
|
||||
#### How do I get support?
|
||||
|
||||
It is very simple to open a support case 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.
|
||||
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.
|
||||
|
||||
https://scc.suse.com/cloudsupport
|
||||
|
||||
If the billing mechanism on the primary cluster is active, a support case will be opened. Further details can be found in the Rancher documentation: https://ranchermanager.docs.rancher.com/integrations-in-rancher/cloudmarketplace/supportconfig
|
||||
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).
|
||||
|
||||
#### What are the resource requirements for installing Rancher on EKS?
|
||||
|
||||
Please check the official documentation for best practices deployments.
|
||||
Please check the official documentation for best practices.
|
||||
|
||||
#### Is there any difference between Rancher Prime from the AWS Marketplace and the versions I can run in my own data center?
|
||||
|
||||
@@ -259,15 +249,4 @@ Yes, nodes can run anywhere. SUSE Rancher will count the total number of nodes m
|
||||
|
||||
#### How do I get fixes and updates for Rancher?
|
||||
|
||||
To update the Rancher product to a current version before the marketplace listing is updated, please see the documentation.
|
||||
|
||||
https://ranchermanager.docs.rancher.com/getting-started/installation-andupgrade/install-upgrade-on-a-kubernetes-cluster/upgrades
|
||||
|
||||
### Miscellaneous
|
||||
|
||||
#### Where can I find out more about Rancher?
|
||||
|
||||
More information can be found at the following sites:
|
||||
|
||||
https://ranchermanager.docs.rancher.com/
|
||||
https://www.rancher.com/products/rancher
|
||||
To update the Rancher product to a current version before the marketplace listing is updated, please see the [documentation](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md).
|
||||
|
||||
@@ -15,11 +15,11 @@ Rancher Prime integrates with the Azure Marketplace as a pay-as-you-go (PAYG) of
|
||||
|
||||
## Limitations
|
||||
|
||||
- Currently, you must be running Rancher Manager v2.7.9. When you deploy a supported PAYG version, you will be able to update to newer versions of Rancher Manager when the listing is updated.
|
||||
- Currently, you must be running Rancher v2.7.9. When you deploy a supported PAYG version, you will be able to update to newer versions of Rancher when the listing is updated.
|
||||
|
||||
## How to Use
|
||||
|
||||
1. Complete the [prerequisite steps](../integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/rancher-prime-azure.md).
|
||||
1. Complete the [prerequisite steps](../integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/prerequisites.md).
|
||||
2. [Install the Rancher Prime PAYG offering on the Azure Marketplace](../integrations-in-rancher/cloud-marketplace/azure-marketplace-payg-integration/installing-rancher-prime.md).
|
||||
|
||||
## FAQ
|
||||
@@ -138,7 +138,7 @@ It is possible to set up an annual commitment via an Azure Private Offer, these
|
||||
|
||||
#### Do I need a Kubernetes cluster running in Azure to install Rancher and be billed via the Azure Marketplace?
|
||||
|
||||
Yes. To benefit from monthly billing via Azure, the primary Rancher cluster must be an Azure Kubernetes Service (AKS) cluster running in your Azure account.
|
||||
Yes. To benefit from monthly billing via Azure, the primary Rancher cluster must be an Azure Kubernetes Service (AKS) cluster running in your Azure account.
|
||||
|
||||
#### On which Kubernetes distributions can the Rancher Prime Azure Marketplace listing be deployed?
|
||||
|
||||
@@ -166,7 +166,7 @@ No. There is no choice over the Rancher version when deploying using the Azure M
|
||||
|
||||
#### How often is the listing updated (including the version of Rancher, etc.)?
|
||||
|
||||
The marketplace listing is tied to a specific version of Rancher, usually it is the latest version available at the time the listing was last updated. Typically, the marketplace listing is updated quarterly, or more frequently to address any new security issues. To update Rancher to a current version before the marketplace listing is updated, please see the product documentation.
|
||||
The marketplace listing is tied to a specific version of Rancher, usually it is the latest version available at the time the listing was last updated. Typically, the marketplace listing is updated quarterly, or more frequently to address any new security issues. To update Rancher to a current version before the marketplace listing is updated, please see the following [documentation](../pages-for-subheaders/installation-and-upgrade.md).
|
||||
|
||||
#### I have many Kubernetes clusters across multiple Azure accounts; does the Rancher Prime billing still work and enable tiered pricing?
|
||||
|
||||
@@ -194,7 +194,7 @@ No. You need to deploy Rancher Prime with the Azure Marketplace listing and migr
|
||||
|
||||
#### How do I get support?
|
||||
|
||||
It is very simple to open a support case with SUSE for Rancher Prime. Create a ‘supportconfig’ via the Rancher UI (click Get Support under the hamburger menu and follow instructions), then upload the ‘supportconfig’ output to the SUSE Customer Center. If the billing mechanism is active, a support case will be opened. See Supportconfig bundle in the Rancher documentation for more details.
|
||||
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 (click Get Support under the hamburger menu and follow instructions), then upload the ‘supportconfig’ output to the SUSE Customer Center. If the billing mechanism is active, a support case will be opened. See Supportconfig bundle in the Rancher [documentation](../integrations-in-rancher/cloud-marketplace/supportconfig.md) for more details.
|
||||
|
||||
:::note
|
||||
|
||||
@@ -204,11 +204,11 @@ For deployments where Rancher Prime is managing multiple downstream clusters, be
|
||||
|
||||
#### What are the resource requirements for installing Rancher on AKS?
|
||||
|
||||
Check the official documentation for best practices. Is there any difference between Rancher Prime from the Azure
|
||||
Check the official documentation for [best practices](../pages-for-subheaders/installation-requirements.md#hosted-kubernetes).
|
||||
|
||||
#### Marketplace and the versions I can run in my own data center?
|
||||
#### Is there any difference between Rancher Prime from Azure Marketplace and the versions I can run in my own data center?
|
||||
|
||||
Rancher Prime available in the Azure Marketplace is the same product, with the same functionality that you would install manually in the cloud or on-premises.The only difference between deploying manually and deploying via the marketplace listing is the billing route.
|
||||
Rancher Prime available in the Azure Marketplace is the same product, with the same functionality that you would install manually in the cloud or on-premises. The only difference between deploying manually and deploying via the marketplace listing is the billing route.
|
||||
|
||||
#### Does the primary cluster (responsible for billing) need to run 24/7?
|
||||
|
||||
@@ -224,4 +224,4 @@ If the Racher Prime cluster is offline or disconnected from the Azure billing fr
|
||||
|
||||
#### How do I get fixes and updates for Rancher?
|
||||
|
||||
To update the Rancher product to a current version before the marketplace listing is updated, see Upgrades in the official documentation.
|
||||
To update the Rancher product to a current version before the marketplace listing is updated, please see the [documentation](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md).
|
||||
|
||||
Reference in New Issue
Block a user