mirror of
https://github.com/qdrant/landing_page.git
synced 2026-09-25 22:18:30 +02:00
Fix typos
This commit is contained in:
Bastian Hofmann
@@ -97,4 +97,4 @@ You can also scale your cluster both horizontally and vertically. Read more in [
|
||||
|
||||
If a new Qdrant version becomes available, you can upgrade your cluster. See [**Cluster Upgrades**](/documentation/cloud/cluster-upgrades/).
|
||||
|
||||
For more information on creating backups of a cluster and restore from them, see [**Backups**](/documentation/cloud/backups/).
|
||||
For more information on creating and restoring backups of a cluster, see [**Backups**](/documentation/cloud/backups/).
|
||||
|
||||
@@ -9,11 +9,11 @@ aliases:
|
||||
|
||||
# Pricing & Payments
|
||||
|
||||
Qdrant database clusters in Qdrant Cloud are prices based on CPU, memory, and disk storage usage. To get a clearer idea for the pricing structure, based on the amounts of vectors you want to store, please use our [Pricing Calculator](https://cloud.qdrant.io/calculator).
|
||||
Qdrant database clusters in Qdrant Cloud are priced based on CPU, memory, and disk storage usage. To get a clearer idea for the pricing structure, based on the amounts of vectors you want to store, please use our [Pricing Calculator](https://cloud.qdrant.io/calculator).
|
||||
|
||||
## Billing
|
||||
|
||||
The costs for Qdrant Cloud database clusters can be paied either through a credit card or through the AWS, GCP, or Azure Marketplace.
|
||||
You can pay for your Qdrant Cloud database clusters either with a credit card or through an AWS, GCP, or Azure Marketplace subscription.
|
||||
|
||||
Your payment method is charged at the beginning of each month for the previous month's usage. There is no difference in pricing between the different payment methods.
|
||||
|
||||
|
||||
@@ -45,10 +45,10 @@ The following functionality is available.
|
||||
|
||||
### Renaming an account
|
||||
|
||||
If you have use multiple accounts for different purposes, it is a good idea to give them descriptive names, for example *Development*, *Production*, *Testing*. You can also choose which account should be the default one, when you log in.
|
||||
If you use multiple accounts for different purposes, it is a good idea to give them descriptive names, for example *Development*, *Production*, *Testing*. You can also choose which account should be the default one, when you log in.
|
||||
|
||||
|
||||
|
||||
### Deleting an account
|
||||
|
||||
When you delete an account, all database clusters and data associated with it will also be deleted.
|
||||
When you delete an account, all database clusters and associated data will be deleted.
|
||||
|
||||
@@ -13,7 +13,7 @@ You can use [Qdrant Cloud's UI](/documentation/cloud/create-cluster/) to create
|
||||
|
||||
Qdrant Hybrid Cloud ensures data privacy, deployment flexibility, low latency, and delivers cost savings, elevating standards for vector search and AI applications.
|
||||
|
||||
**How it works:** Qdrant Hybrid Cloud relies on Kubernetes and works with any standard compliant Kubernetes distribution. When you onboard a Kubernetes cluster as a Hybrid Cloud Environment, you can deploy the Qdrant Kubernetes Operator and Cloud Agent into this cluster. These will manage Qdrant databases within your Kubernetes cluster and establish an outgoing connection to Qdrant Cloud to transport telemetry and receive management instructions. You can then benefit from the same cloud management features and transport telemetry as is available with any managed Qdrant Cloud cluster.
|
||||
**How it works:** Qdrant Hybrid Cloud relies on Kubernetes and works with any standard compliant Kubernetes distribution. When you onboard a Kubernetes cluster as a Hybrid Cloud Environment, you can deploy the Qdrant Kubernetes Operator and Cloud Agent into this cluster. These will manage Qdrant databases within your Kubernetes cluster and establish an outgoing connection to Qdrant Cloud to transport telemetry and receive management instructions. You can then benefit from the same cloud management features and transport telemetry that is available with any managed Qdrant Cloud cluster.
|
||||
|
||||
<aside role="status">Qdrant Cloud does not connect to the API of your Kubernetes cluster, cloud provider, or any other platform APIs.</aside>
|
||||
|
||||
@@ -29,8 +29,8 @@ The Qdrant Kubernetes Operator will manage the Qdrant databases within your Kube
|
||||
|
||||
Both component's access is limited to the Kubernetes namespace that you chose during the onboarding process.
|
||||
|
||||
After the initial onboarding, the lifecycle of these components will be controlled by the Qdrant Cloud platform through a built-in Helm controller.
|
||||
After the initial onboarding, the lifecycle of these components will be controlled by the Qdrant Cloud platform via the built-in Helm controller.
|
||||
|
||||
You don't need to expose your Kubernetes Cluster to the Qdrant Cloud platform, you don't need to open any ports for incoming traffic and you don't need to provide any Kubernetes or cloud provider credentials to the Qdrant Cloud platform.
|
||||
You don't need to expose your Kubernetes Cluster to the Qdrant Cloud platform, you don't need to open any ports for incoming traffic, and you don't need to provide any Kubernetes or cloud provider credentials to the Qdrant Cloud platform.
|
||||
|
||||
|
||||
|
||||
@@ -16,9 +16,9 @@ Note that in the "Kubernetes Configuration" section you can additionally configu
|
||||
|
||||
These settings can also be changed after the cluster is created on the cluster detail page.
|
||||
|
||||
### Authentication at your Qdrant clusters
|
||||
### Authentication to your Qdrant clusters
|
||||
|
||||
In Hybrid Cloud the authentication information is provided with Kubernetes secrets.
|
||||
In Hybrid Cloud the authentication information is provided by Kubernetes secrets.
|
||||
|
||||
You can configure authentication for your Qdrant clusters in the "Configuration" section of the Qdrant Cluster detail page. There you can configure the Kubernetes secret name and key to be used as an API key and/or read-only API key.
|
||||
|
||||
@@ -71,7 +71,7 @@ You can also expose the database outside the Kubernetes cluster with a `LoadBala
|
||||
|
||||
The service type and necessary annotations can be configured in the "Kubernetes Configuration" section during cluster creation, or on the cluster detail page.
|
||||
|
||||
Especially if you create a LoadBalancer Service, you may need to provider annotations for the loadbalancer configration. Please refer to the documention of your cloud provider for more details.
|
||||
Especially if you create a LoadBalancer Service, you may need to provide annotations for the loadbalancer configration. Please refer to the documention of your cloud provider for more details.
|
||||
|
||||
Examples:
|
||||
|
||||
@@ -124,7 +124,7 @@ spec:
|
||||
|
||||
Please refer to the Kubernetes, ingress controller and cloud provider documention for more details.
|
||||
|
||||
If you expose the database with such a way, you will be able to see this also reflected as an endpoint on the cluster detail page. And will see the Qdrant database dashboard link pointing to it.
|
||||
If you expose the database like this, you will be able to see this also reflected as an endpoint on the cluster detail page. And will see the Qdrant database dashboard link pointing to it.
|
||||
|
||||
### Configuring TLS
|
||||
|
||||
@@ -133,7 +133,7 @@ If you want to configure TLS for accessing your Qdrant database in Hybrid Cloud,
|
||||
* You can offload TLS at the ingress or loadbalancer level.
|
||||
* You can configure TLS directly in the Qdrant database.
|
||||
|
||||
If you want to configure TLS directly in the Qdrant database, you can provide a secret with the TLS certificate and key in the "Configuration" section of the Qdrant Cluster detail page. There you can configure the Kubernetes secret name and key to be used as the certificate and key.
|
||||
If you want to configure TLS directly in the Qdrant database, you can reference a secret containing the TLS certificate and key in the "Configuration" section of the Qdrant Cluster detail page.
|
||||
|
||||
To create such a secret, you can use `kubectl`:
|
||||
|
||||
|
||||
@@ -69,7 +69,7 @@ You can also configure the StorageClass and VolumeSnapshotClass to use for the Q
|
||||
|
||||
5. (Optional) If you have special requirements for any of the following, activate the **Show advanced configuration** option:
|
||||
|
||||
- If you require to use a proxy to connect from your infrastructure to the Qdrant Cloud API, you can specify the proxy URL, credentials and cetificates.
|
||||
- If you use a proxy to connect from your infrastructure to the Qdrant Cloud API, you can specify the proxy URL, credentials and cetificates.
|
||||
- Container registry URL for Qdrant Operator and Agent images. The default is <https://registry.cloud.qdrant.io/qdrant/>.
|
||||
- Helm chart repository URL for the Qdrant Operator and Agent. The default is <oci://registry.cloud.qdrant.io/qdrant-charts>.
|
||||
- Log level for the operator and agent
|
||||
|
||||
Reference in New Issue
Block a user