Skip to content

Commit

Permalink
PR link level fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
jdreinhardt authored and sunilarjun committed Nov 1, 2024
1 parent 69d8b5b commit fc94c16
Showing 1 changed file with 7 additions and 7 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ The marketplace listing is tied to a specific version of NeuVector, usually the

Typically, the marketplace listing is updated quarterly, or more frequently if there are security issues. NeuVector itself is updated with major, minor, or patch versions every 6-8 weeks.

To update the NeuVector product to a current version before the marketplace listing is updated, please see [Updating NeuVector](../updating/updating).
To update the NeuVector product to a current version before the marketplace listing is updated, please see [Updating NeuVector](../../updating/updating).

***I have many Kubernetes clusters across multiple cloud accounts, does the NeuVector billing still work and enable tiered pricing?***

Expand All @@ -193,7 +193,7 @@ Billing is routed to the cloud provider account in which the primary cluster is

***I have multiple independent clusters, each running a separate installation of the NeuVector Prime marketplace listing, how is this billed?***

As the NeuVector deployments are independent, each cluster is billed separately from the others. It is not possible to benefit from tiered pricing across clusters unless the NeuVector deployments are federated. Federation requires that only the primary cluster (not downstream remotes) be installed with the NeuVector Prime marketplace listing. Learn more about federation in [Enterprise Multi-Cluster Management](../navigation/multicluster).
As the NeuVector deployments are independent, each cluster is billed separately from the others. It is not possible to benefit from tiered pricing across clusters unless the NeuVector deployments are federated. Federation requires that only the primary cluster (not downstream remotes) be installed with the NeuVector Prime marketplace listing. Learn more about federation in [Enterprise Multi-Cluster Management](../../navigation/multicluster).

If Federation is not possible, consider custom terms from SUSE.

Expand All @@ -202,7 +202,7 @@ If Federation is not possible, consider custom terms from SUSE.
The primary cluster must be running on a managed kubernetes cluster. This is EKS in the AWS Cloud, or AKS in Azure. The cluster must be running the NeuVector Prime marketplace listing.

:::warning attention
There MUST be network connectivity between the controllers in each cluster on the required ports. The controller is exposed externally to its cluster by either a primary or remote service. See [Enterprise Multi-Cluster Management](../navigation/multicluster) for more information on federating clusters.
There MUST be network connectivity between the controllers in each cluster on the required ports. The controller is exposed externally to its cluster by either a primary or remote service. See [Enterprise Multi-Cluster Management](../../navigation/multicluster) for more information on federating clusters.
:::

***I have purchased multiple SUSE products from the public cloud marketplace (e.g., Rancher Prime and NeuVector Prime), does the marketplace billing method still work?***
Expand All @@ -215,7 +215,7 @@ Yes, providing it is an EKS cluster in AWS, or AKS in Azure. Simply deploy the A

***I already have an existing cluster with NeuVector deployed, can I just install the NeuVector Prime marketplace listing and have support billed via the cloud marketplace?***

Yes. This is possible by redeploying the NeuVector Prime from the cloud provider marketplace listing. Please follow the documentation to [back up the existing NeuVector configuration](../deploying/production#backups-and-persistent-data), as it may be necessary to [restore the configuration](../deploying/restore) into the new deployment.
Yes. This is possible by redeploying the NeuVector Prime from the cloud provider marketplace listing. Please follow the documentation to [back up the existing NeuVector configuration](../../deploying/production#backups-and-persistent-data), as it may be necessary to [restore the configuration](../../deploying/restore) into the new deployment.

## Technical (Product)

Expand Down Expand Up @@ -249,19 +249,19 @@ Depending on when in the month the primary cluster gets reconnected you may have

***How do I get fixes and updates to NeuVector?***

NeuVector is updated with major, minor, or patch versions every 6-8 weeks. To update NeuVector to a current version before the NeuVector Prime marketplace listing is updated, please see [Updating NeuVector](../updating/updating).
NeuVector is updated with major, minor, or patch versions every 6-8 weeks. To update NeuVector to a current version before the NeuVector Prime marketplace listing is updated, please see [Updating NeuVector](../../updating/updating).

## Miscellaneous

***Where can I find out more about the NeuVector Prime Marketplace listing?***

- For AWS:

- You can find out more about the NeuVector Prime AWS Marketplace listing in the [NeuVector documentation](../deploying/public-cloud/awsmarketplace).
- You can find out more about the NeuVector Prime AWS Marketplace listing in the [NeuVector documentation](awsmarketplace).

- For Azure:

- You can find out more about the NeuVector Prime AWS Marketplace listing in the [NeuVector documentation](../deploying/public-cloud/azuremarketplace).
- You can find out more about the NeuVector Prime AWS Marketplace listing in the [NeuVector documentation](azuremarketplace).

***Where can I find out more about NeuVector?***

Expand Down

0 comments on commit fc94c16

Please sign in to comment.