Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix spelling typo #2315

Merged
merged 1 commit into from
May 1, 2024
Merged

Fix spelling typo #2315

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/partials/cmx/_billing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
Clusters created with the compatiblity matrix are billed by the minute. Per-minute billing begins when the cluster reaches a `running` status and ends when the cluster is deleted. The compatibility matrix marks a cluster as `running` when a working kubeconfig for the cluster is accessible.
Clusters created with the compatibility matrix are billed by the minute. Per-minute billing begins when the cluster reaches a `running` status and ends when the cluster is deleted. The compatibility matrix marks a cluster as `running` when a working kubeconfig for the cluster is accessible.

You are billed only for the time that the cluster is in a `running` status. You are _not_ billed for the time that it takes the compatibility matrix to create and tear down clusters, including when the cluster is in an `assigned` status.

To create clusters with the compatibility matrix, you must have credits in your vendor portal account.
To request credits, log in to the vendor portal and go to [**Compatibility Matrix > Request more credits**](https://vendor.replicated.com/compatibility-matrix).
To request credits, log in to the vendor portal and go to [**Compatibility Matrix > Request more credits**](https://vendor.replicated.com/compatibility-matrix).
4 changes: 2 additions & 2 deletions docs/partials/cmx/_overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ The Replicated compatibility matrix quickly provisions ephemeral clusters of dif

You can use the compatibility matrix to get kubectl access to running clusters within minutes or less. This allows you to more easily test your code in a range of different environments before releasing to customers.

Example use cases for the compatiblity matrix include:
Example use cases for the compatibility matrix include:
* Run tests before releasing a new version of your application to validate compatibility with supported Kubernetes distributions
* Get access to a cluster to develop on and quickly test changes
* Reproduce a reported issue on a customer-representative environment for troubleshooting
* Reproduce a reported issue on a customer-representative environment for troubleshooting
Loading