public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 20:48:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

FAQ grammar check

Browse Source
This commit is contained in:
LucasSaintarbor
2024-01-04 16:45:44 -08:00
parent 5569325344
commit f03ac43b69
2 changed files with 63 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages-for-subheaders/aws-marketplace-payg-integration.md
+39 -36
View File
@@ -34,52 +34,50 @@ By selecting the Rancher Prime listing from the AWS Marketplace, customers can d
#### Where do I find the Rancher Prime listings?
The listings can be found in the AWS Marketplace, there are two listings:
There are two listings in the AWS Marketplace. They are:
- Rancher Prime
- Rancher Prime (EMEA Orders Only)
- [Rancher Prime](https://aws.amazon.com/marketplace/pp/prodview-f2bvszurj2p2c)
- [Rancher Prime (EMEA Orders Only)](https://aws.amazon.com/marketplace/pp/prodview-ocgjwd5c2aj5i)
#### Why are there 2 listings, which one should I use?
#### Why are there two listings? Which one should I use?
We have 2 listings for Rancher Prime, "EU, EEA, or UK Orders" and "no EU, EEA, or UK Orders", you should pick the listing that reflects where your AWS account gets billed.
We have two listings for Rancher Prime, "EU, EEA, or UK Orders" and "non EU, EEA, or UK Orders." You should pick the listing that reflects where your AWS account gets billed.
#### Are these listings available in all countries?
The Rancher listing on AWS is not available to purchase in all countries.
No. The Rancher listing on AWS is not available to purchase in all countries.
Your billing country is based on the AWS Account ID used to do the deployment.
Please read the addendum at the end of this FAQ for a list of countries that can and cannot transact Rancher Prime via the AWS Marketplace.
#### My AWS account is in the USA, but I want to deploy Rancher in another AWS region, a region that is in a country where I currently cannot transact Rancher Prime, is this possible?
#### My AWS account is in the USA, but I want to deploy Rancher in another AWS region, a region that is in a country where I currently cannot transact Rancher Prime. Is this possible?
Yes. As long as your AWS account is billed to one of the allowed countries, it is possible to deploy Rancher in any AWS regions.
#### Is this listing available in China?
Whilst it is not possible to transact/bill Rancher Prime in China, it is possible to deploy into AWS regions in China.
While it is not possible to transact/bill Rancher Prime in China, it is possible to deploy into AWS regions in China.
Please read the addendum at the end of this FAQ for a list of countries that can and cannot transact Rancher Prime via the AWS Marketplace.
#### Can I still deploy Rancher using the ‘Rancher Setup’ listing from the AWS Marketplace?
#### 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. Please refer to the best practice documentation.
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.
"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).
### Billing
#### I have an existing Rancher Prime subscription; can I use this on AWS?
#### I have an existing Rancher Prime subscription. Can I use this on AWS?
BYOS (Bring Your Own Subscription) Rancher deployments are supported on AWS, however, billing will not be via the AWS Marketplace. Once the existing subscription term ends, you can purchase Rancher Prime via the AWS Marketplace and reconfigure your cluster to support monthly billing via AWS.
BYOS (Bring Your Own Subscription) Rancher deployments are supported on AWS; however, billing will not be via the AWS Marketplace. Once the existing subscription term ends, you can purchase Rancher Prime via the AWS Marketplace and reconfigure your cluster to support monthly billing via AWS.
#### I have an existing Rancher Subscription purchased via the ’Rancher Premium Support’ listing on AWS; is this transferable to the new model?
#### I have an existing Rancher Subscription purchased via the ’Rancher Premium Support’ listing on AWS. Isthis transferable to the new model?
No. A new deployment of Rancher Prime is required to benefit from the new monthly billing model.
#### 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?
@@ -91,12 +89,12 @@ total.
- An average node count is calculated for the month.
- There is a monthly usage charge for each node in the average node count.
- The monthly usage charge depends on the number of nodes in use.
- There is a 5-node minimum, if the average node count is less than 5 nodes, the
- There is a 5-node minimum; if the average node count is less than 5 nodes, the
charge will be for 5 nodes.
#### What are the pricing tiers?
Rancher Prime has different pricing tiers when purchasing via the AWS Marketplace. This is based on the number of nodes which Rancher is managing. Details of the tiers are below, please check the listing for further pricing information.
Rancher Prime has different pricing tiers when purchasing via the AWS Marketplace. This is based on the number of nodes which Rancher is managing. Details of the tiers are below. Please check the listing for further pricing information.
| Tier | Nodes (from) | Nodes (to) |
| :------: | :----------: | :---------: |
@@ -117,11 +115,17 @@ Rancher can be deployed manually using the standard documentation and repositori
The average node count is calculated by adding the number of managed nodes (counted hourly) and dividing by the number of hours Rancher has been active in the billing cycle.
Below are 3 examples of how the average node count is calculated. Check the table below for the details. N.B. in our example month, we are using 730 hours, this may differ depending on the number of days in the month and the billing cycle.
Below are three examples of how the average node count is calculated. Check the table below for the details.
:::note
In our example month, we are using 730 hours; this may differ depending on the number of days in the month and the billing cycle.
:::
- **Static usage:** Using Rancher to manage 10 nodes, for 1 month (730 hours) with no additional nodes added in the month.
- **Bursting Model:** Using Rancher to manage 10 nodes for 3 weeks (562 hours) in the month, bursting to 30 nodes for 1 week (168 hours).
- **Transient cluster:** A temporary deployment of Rancher on 20 nodes for 2 weeks (336 hours)
- **Transient cluster:** A temporary deployment of Rancher on 20 nodes for 2 weeks (336 hours).
| | Hours Active (Hours Rancher is active in the month) | Nodes (Managed Nodes counted at each check-in) | Usage total (Sum of nodes reported at each check-in) | Average Node Count (Usage total / hours active) | Note |
| ----------------- | :--: | :------------------------: | :----: | :--: | :------------------------------: |
@@ -131,21 +135,21 @@ Below are 3 examples of how the average node count is calculated. Check the tabl
#### Are special commercial terms available?
Depending on the deployment, it may be possible to secure special commercial terms (e.g., an annual subscription). This will be handled via an AWS Private offer, please contact SUSE for more information.
Depending on the deployment, securing special commercial terms (e.g., an annual subscription) may be possible. This will be handled via an AWS Private offer. Please contact SUSE for more information.
#### Can my spend on Rancher Prime count towards my AWS Enterprise Discount Program?
Yes, it can. Please contact your AWS Sales Team for more details.
Yes. Please contact your AWS Sales Team for more details.
#### How do I purchase Rancher for additional nodes?
Once Rancher has been deployed from the listing on AWS and billing is active, there is no need to make a specific purchase for additional nodes. Billing is dynamic and based on the number of nodes Rancher is managing. Just deploy or on-board additional clusters to Rancher as needed.
Once Rancher has been deployed from the listing on AWS and billing is active, there is no need to make a specific purchase for additional nodes. Billing is dynamic and based on the number of nodes Rancher is managing. Just deploy or onboard additional clusters to Rancher as needed.
#### Is this an annual commitment, will it auto-renew?
By default, the Rancher Prime listing in AWS is billed on a monthly cycle, based on usage. Billing is on-going for as long as Rancher is deployed.
By default, the Rancher Prime listing in AWS is billed on a monthly cycle, based on usage. Billing is ongoing for as long as Rancher is deployed.
It is possible to set up an annual commitment via an AWS Private Offer, these will need to be reviewed and renewed at the end of the term, or the deployment will drop back to the default monthly billing cycle.
It is possible to set up an annual commitment via an AWS Private Offer; these will need to be reviewed and renewed at the end of the term, or the deployment will drop back to the default monthly billing cycle.
### Technical (Billing)
@@ -153,9 +157,9 @@ It is possible to set up an annual commitment via an AWS Private Offer, these wi
Yes. To benefit from monthly billing via the Marketplace, the primary Rancher cluster must be an EKS Cluster running in your AWS Account.
#### On which Kubernetes distributions can the AWS Marketplace listing be deployed?
#### Which Kubernetes distributions can the AWS Marketplace listing be deployed on?
The AWS Marketplace listing for Rancher Prime with Marketplace billing must be deployed on Amazon EKS. Downstream clusters / managed worker nodes can be running on any CNCF compliant Kubernetes platform, EKS, EKS-A, Rancher Kubernetes Engine, etc.
The AWS Marketplace listing for Rancher Prime with Marketplace billing must be deployed on Amazon EKS. Downstream clusters / managed worker nodes can run on any CNCF compliant Kubernetes platform, EKS, EKS-A, Rancher Kubernetes Engine, etc.
#### What is the deployment mechanism?
@@ -185,14 +189,13 @@ Billing through AWS Marketplace may not be supported with previous versions.
#### How often is the listing updated (including the version of Rancher, etc.)?
Cloud marketplace listings are tied to a specific version of Rancher, usually the latest
version available at the time of listing. Typically, these are updated quarterly, or more frequently if there are security issues.
The marketplace listing is tied to a specific version of Rancher, usually the latest version available at the time of listing. Typically, these are updated quarterly, or more frequently if there are security issues.
#### I have many Kubernetes clusters across multiple AWS accounts, does the Rancher Prime billing still work and enable tiered pricing?
Yes. Downstream clusters managed by Rancher can be deployed across single or multiple AWS accounts, on-premises, or even in other public clouds. Downstream nodes will report up to the primary Rancher deployment. Tiered pricing is enabled and billing will be routed to the AWS account in which the primary cluster is running.
#### I have multiple independent clusters, each running a separate installation of the AWS Marketplace listing for Rancher Prime, how is this billed?
#### I have multiple independent clusters, each running a separate installation of the AWS Marketplace listing for Rancher Prime. How is this billed?
As the Rancher Prime deployments are independent, each deployment is billed separately from the others. It is not possible to benefit from tiered pricing.
@@ -200,17 +203,17 @@ As the Rancher Prime deployments are independent, each deployment is billed sepa
The primary Rancher cluster must be running on EKS in the AWS Cloud and running the AWS Marketplace listing for Rancher. To benefit from tiered pricing, managed clusters (downstream clusters) should be connected to the primary Rancher cluster.
#### I have purchased multiple SUSE products from the AWS Marketplace (e.g., SUSE Manager, NeuVector Prime and now Rancher Prime), does the AWS Marketplace billing method still work?
#### I have purchased multiple SUSE products from the AWS Marketplace (e.g., SUSE Manager, NeuVector Prime and now Rancher Prime). Does the AWS Marketplace billing method still work?
Yes. The billing mechanism of each deployment is independent, each product will be billed separately via the AWS Marketplace.
#### I already have an existing EKS cluster in place and want to add Rancher and have this billed via Marketplace. Is this possible?
Yes, simply deploy the AWS Marketplace listing for Rancher Prime.
Yes. Simply deploy the AWS Marketplace listing for Rancher Prime.
#### I already have an existing cluster, with Rancher deployed, can I just install the marketplace version and have support billed via the AWS Marketplace?
#### I already have an existing cluster, with Rancher deployed. Can I just install the marketplace version and have support billed via the AWS Marketplace?
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.
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](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/upgrades.md) and be sure to back up the existing Rancher configuration.
@@ -238,7 +241,7 @@ To ensure continuity with support, it is recommended that the primary Rancher cl
There may be multiple reasons why the primary cluster is unable to connect to the AWS framework, but it is the customer’s responsibility to ensure that the primary cluster is active and connected. Whilst the cluster is not connected to the billing framework, it is not possible to raise a support request.
#### My primary cluster has been offline, what will happen with billing when reconnected?
#### My primary cluster has been offline. What will happen with billing when reconnected?
If the primary cluster is offline or disconnected from the AWS billing framework for a period of time, when it reconnects, the stored usage data will be uploaded to AWS and will appear on your next AWS bill.
@@ -246,7 +249,7 @@ Depending on when in the month the primary cluster gets reconnected you may have
#### Can the managed worker nodes reside on premises, at the edge or even on another cloud provider?
Yes, nodes can run anywhere. SUSE Rancher will count the total number of nodes managed regardless of where they are deployed.
Yes. Nodes can run anywhere. SUSE Rancher will count the total number of nodes managed regardless of where they are deployed.
#### How do I get fixes and updates for Rancher?
docs/pages-for-subheaders/azure-marketplace-payg-integration.md
+24 -22
View File
@@ -36,20 +36,20 @@ By selecting the Rancher Prime listing in the Azure Marketplace, customers can d
There are two listings in the Azure Marketplace. They are:
- Rancher Prime with 24x7 Support
- Rancher Prime with 24x7 Support (EMEA Orders Only)
- [Rancher Prime with 24x7 Support](https://portal.azure.com/#view/Microsoft_Azure_Marketplace/GalleryItemDetailsBladeNopdl/id/suse.rancher-prime-llc/selectionMode~/false/resourceGroupId//resourceGroupLocation//dontDiscardJourney~/false/selectedMenuId/home/launchingContext~/%7B%22galleryItemId%22%3A%22suse.rancher-prime-llcpay-as-you-go%22%2C%22source%22%3A%5B%22GalleryFeaturedMenuItemPart%22%2C%22VirtualizedTileDetails%22%5D%2C%22menuItemId%22%3A%22home%22%2C%22subMenuItemId%22%3A%22Search%20results%22%2C%22telemetryId%22%3A%221dafcf16-920e-46ea-80c9-dc85c6bd3a17%22%7D/searchTelemetryId/c2300fb7-ba7b-462a-ba57-a37cb5e2822d)
- [Rancher Prime with 24x7 Support (EMEA Orders Only)](https://portal.azure.com/#view/Microsoft_Azure_Marketplace/GalleryItemDetailsBladeNopdl/id/suseirelandltd1692213356027.rancher-prime-ltd/selectionMode~/false/resourceGroupId//resourceGroupLocation//dontDiscardJourney~/false/selectedMenuId/home/launchingContext~/%7B%22galleryItemId%22%3A%22suseirelandltd1692213356027.rancher-prime-ltdpay-as-you-go%22%2C%22source%22%3A%5B%22GalleryFeaturedMenuItemPart%22%2C%22VirtualizedTileDetails%22%5D%2C%22menuItemId%22%3A%22home%22%2C%22subMenuItemId%22%3A%22Search%20results%22%2C%22telemetryId%22%3A%22c6b1d79a-b577-47b0-90e5-41e6c49688ab%22%7D/searchTelemetryId/1793144d-e0d9-466e-8e36-dfeddc73163b)
#### Why are there 2 listings, which one should I use?
#### Why are there two listings? Which one should I use?
There are two listings for Rancher Prime to accommodate Microsoft Azure billing regions. You should pick the listing that reflects where your Azure account gets billed.
#### Are these listings available in all countries?
No, due to billing limitations and other restrictions, the Rancher Prime Azure Marketplace listing may not be purchasable in all countries. The Azure account you use for deployment determines your billing country. Contact your Azure Sales Team for more details.
No. Due to billing limitations and other restrictions, the Rancher Prime Azure Marketplace listing may not be purchasable in all countries. The Azure account you use for deployment determines your billing country. Contact your Azure Sales Team for more details.
#### My Azure account is in the USA, but I want to deploy Rancher in another Azure region, a region that is in a country where I currently cannot transact Rancher Prime, is this possible?
#### My Azure account is in the USA, but I want to deploy Rancher in another Azure region, a region that is in a country where I currently cannot transact Rancher Prime. Is this possible?
Yes, as long as your Azure account is billed to one of the allowed countries, it is possible to deploy Rancher Prime in any Azure region.
Yes. As long as your Azure account is billed to one of the allowed countries, it is possible to deploy Rancher Prime in any Azure region.
#### Is this listing available in China?
@@ -63,7 +63,7 @@ Self-installed BYOS (Bring Your Own Subscription) Rancher Prime deployments are
#### I have an existing deployment covered by a Rancher subscription; can I use this new listing in the Azure Marketplace for new deployments?
Yes, the listing works independently from your existing Rancher Prime subscriptions. Only deployments through the marketplace listing will be billed through Azure. Support is always direct from SUSE.
Yes. the listing works independently from your existing Rancher Prime subscriptions. Only deployments through the marketplace listing will be billed through Azure. Support is always direct from SUSE.
#### Tell me more about how the billing for Rancher Prime works via Azure?
@@ -74,11 +74,11 @@ When purchasing Rancher Prime via the Azure Marketplace, the billing is as follo
- An average node count is calculated for the month.
- There is a monthly usage charge for each node in the average node count.
- The monthly usage charge depends on the number of nodes in use.
- There is a 5-node minimum, if the average node count is less than 5 nodes, the charge will be for 5 nodes.
- There is a 5-node minimum; if the average node count is less than 5 nodes, the charge will be for 5 nodes.
#### What are the pricing tiers?
Rancher Prime has different pricing tiers when purchasing via the Azure Marketplace. This is based on the number of nodes which Rancher is managing.Details of the tiers are shown below, please check the listing for further pricing information.
Rancher Prime has different pricing tiers when purchasing via the Azure Marketplace. This is based on the number of nodes that Rancher is managing. Details of the tiers are shown below. Please check the listing for further pricing information.
| Tier | Nodes (from) | Nodes (to) |
| :------: | :----------: | :---------: |
@@ -104,7 +104,7 @@ In our example month, we are using 730 hours; this may differ depending on the n
:::
- **Static Usage:**
Using Rancher to manage 10 nodes, for 1 month (730 hours) with no additional nodes added in the month.
Using Rancher to manage 10 nodes for 1 month (730 hours) with no additional nodes added in the month.
- **Bursting Model:**
Using Rancher to manage 10 nodes for 3 weeks (562 hours) in the month and bursting to 30 nodes for 1 week (168 hours).
- **Transient Cluster:**
@@ -118,21 +118,21 @@ A temporary deployment of Rancher on 20 nodes for 2 weeks (336 hours).
#### Are special commercial terms available?
Depending on the deployment, it may be possible to secure special commercial terms, such as an annual subscription. This will be handled via an Azure private offer, contact SUSE for more information.
Depending on the deployment, securing special commercial terms (e.g., an annual subscription) may be possible. This will be handled via an Azure private offer. Please contact SUSE for more information.
#### Can my spend on Rancher Prime count towards my MACC Program?
Yes, it can. Contact your Azure Sales Team for more details.
Yes. Contact your Azure Sales Team for more details.
#### How do I purchase Rancher for additional nodes?
Once Rancher Prime has been deployed from the Azure Marketplace and billing is active, there is no need to make a specific purchase for additional nodes. Billing is dynamic and based on the number of nodes Rancher is managing. Just deploy or on-board additional clusters to Rancher as needed.
Once Rancher Prime has been deployed from the Azure Marketplace and billing is active, there is no need to make a specific purchase for additional nodes. Billing is dynamic and based on the number of nodes Rancher is managing. Just deploy or onboard additional clusters to Rancher as needed.
#### Is this an annual commitment, will it auto-renew?
By default, the Rancher Prime listing is billed on a monthly cycle, based on usage. Billing is on-going for as long as Rancher Prime is deployed.
By default, the Rancher Prime listing is billed on a monthly cycle, based on usage. Billing is ongoing for as long as Rancher Prime is deployed.
It is possible to set up an annual commitment via an Azure Private Offer, these will need to be reviewed and renewed at the end of the term, or the deployment will drop back to the default monthly billing cycle.
It is possible to set up an annual commitment via an Azure Private Offer; these will need to be reviewed and renewed at the end of the term, or the deployment will drop back to the default monthly billing cycle.
### Technical
@@ -140,7 +140,7 @@ It is possible to set up an annual commitment via an Azure Private Offer, these
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?
#### Which Kubernetes distributions can the Rancher Prime Azure Marketplace listing be deployed on?
The Rancher Prime marketplace listing must be deployed on Azure Kubernetes Service (AKS). Downstream/managed clusters can run any supported Kubernetes platform: RKE, RKE2, EKS, GKE, vanilla Kubernetes, OpenShift, Mirantis Kubernetes Engine, etc. See Supported Platforms for more details.
@@ -178,7 +178,7 @@ The marketplace listing is tied to a specific version of Rancher, usually it is
Yes. Downstream/managed clusters can be deployed across single or multiple Azure accounts, on-premises, and in other public clouds. Downstream/managed nodes report up to Rancher Prime, enabling tiered pricing with billing routed to the Azure account in which the managing Rancher Prime cluster is running.
#### I have multiple independent clusters, each running a separate installation of the Rancher Prime Azure Marketplace listing; how is this billed?
#### I have multiple independent clusters, each running a separate installation of the Rancher Prime Azure Marketplace listing. How is this billed?
As the Rancher Prime deployments are independent, each deployment is billed separately from the others. It is not possible to benefit from tiered pricing. If managing multiple independent Rancher Prime clusters, consider custom terms from SUSE.
@@ -186,18 +186,20 @@ As the Rancher Prime deployments are independent, each deployment is billed sepa
The primary Rancher Prime cluster must be running on AKS in Microsoft Azure, deployed through the marketplace listing. To benefit from tiered pricing, downstream/managed clusters should be imported into the primary Rancher Prime cluster.
#### I have purchased multiple SUSE products from the Azure Marketplace (e.g., SUSE Manager, NeuVector Prime, Rancher Prime); does the Azure Marketplace billing method still work?
#### I have purchased multiple SUSE products from the Azure Marketplace (e.g., SUSE Manager, NeuVector Prime, Rancher Prime). Does the Azure Marketplace billing method still work?
Yes. The billing mechanisms for the deployments are independent and are billed separately via the Azure Marketplace.
#### I already have an existing AKS cluster in place and want to add Rancher Prime to it and be billed through the Azure Marketplace; is this possible?
#### I already have an existing AKS cluster in place and want to add Rancher Prime to it and be billed through the Azure Marketplace. Is this possible?
Yes, simply deploy the Rancher Prime to the cluster with the Azure Marketplace listing.
Yes. Simply deploy the Rancher Prime to the cluster with the Azure Marketplace listing.
#### I already deployed Rancher to an existing AKS cluster; can I just install the marketplace version to enable Azure Marketplace billing?
#### I already deployed Rancher to an existing AKS cluster. Can I just install the marketplace version to enable Azure Marketplace billing?
No. You need to deploy Rancher Prime with the Azure Marketplace listing and migrate the existing Rancher configuration to this new deployment. Be sure that you back up your existing Rancher configuration.
### Technical (Product)
#### How do I get support?
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.
@@ -224,7 +226,7 @@ To ensure continuity of support, it is recommended that the primary Rancher Prim
There may be multiple reasons why the primary cluster is unable to connect to the Azure billing framework, but it is the customer’s responsibility to ensure that the primary cluster is active and connected. While the cluster is not connected to the billing framework, it is not possible to raise a support request.
#### My primary cluster has been offline; what will happen with billing when reconnected?
#### My primary cluster has been offline. What will happen with billing when reconnected?
If the Racher Prime cluster is offline or disconnected from the Azure billing framework for a period of time, when it reconnects, the stored usage data will be uploaded to Azure and will appear on your next Azure bill. Depending on the month when the primary cluster gets reconnected you may have several months of usage on your next billing cycle.