Skip to content

Commit

Permalink
Merge pull request #1148 from qdrant/feat/bashofmann/private-cloud-pr…
Browse files Browse the repository at this point in the history
…emium

Add docs for private cloud and premium tier
  • Loading branch information
davidmyriel authored Sep 16, 2024
2 parents f446041 + c1b86a0 commit 6dca56c
Show file tree
Hide file tree
Showing 19 changed files with 1,974 additions and 21 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Authentication
weight: 30
---

# Authenticating to Qdrant Cloud
# Database Authentication in Qdrant Managed Cloud

This page shows you how to use the Qdrant Cloud Console to create a custom API key for a cluster. You will learn how to connect to your cluster using the new API key.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ In this case vectors will be stored on the disc in memory-mapped files, and only
The amount of available RAM will significantly affect the performance of the search.
As a rule of thumb, if you keep 2 times less vectors in RAM, the search latency will be 2 times lower.

The speed of disks is also important. [Let us know](mailto:[email protected]) if you have special requirements for a high-volume search.
The speed of disks is also important. [Let us know](/documentation/support/) if you have special requirements for a high-volume search.

## Sub-groups oriented configuration

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -37,4 +37,4 @@ Note, that it is currently not possible to horizontally scale down the cluster i

We will be glad to consult you on an optimal strategy for scaling.

[Let us know](mailto:[email protected]) your needs and decide together on a proper solution.
[Let us know](/documentation/support/) your needs and decide together on a proper solution.
19 changes: 19 additions & 0 deletions qdrant-landing/content/documentation/cloud/premium.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: Premium Tier
weight: 66
---

# Qdrant Cloud Premium Tier

Qdrant Cloud offers an optional premium tier for customers who require additional features and better SLA support levels. The premium tier includes:

* **24/7 Support**: Our support team is available around the clock to help you with any issues you may encounter (compared to 10x5 in standard).
* **Shorter Response Times**: Premium customers receive priority support and can expect faster response times, with shorter SLAs.
* **99.9% Uptime SLA**: We guarantee 99.9% uptime for your Qdrant Cloud clusters (compared to 99.5% in standard).
* **Single Sign-On (SSO)**: Premium customers can use their existing SSO provider to manage access to Qdrant Cloud.
* **VPC Private Links**: Premium customers can connect their Qdrant Cloud clusters to their VPCs using private links (AWS only).
* **Storage encryption with shared keys**: Premium customers can encrypt their data at rest using their own keys (AWS only).

Please refer to the [Qdrant Cloud SLA](https://qdrant.to/sla/) for a detailed definition on uptime and support SLAs.

If you are interested in using switch to Qdrant Cloud Premium, please [contact us](/contact-us/) for more information.
16 changes: 16 additions & 0 deletions qdrant-landing/content/documentation/cloud/qdrant-cloud-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,3 +52,19 @@ If you use multiple accounts for different purposes, it is a good idea to give t
### Deleting an account

When you delete an account, all database clusters and associated data will be deleted.

## Enterprise Single-Sign-On (SSO)

Qdrant Cloud supports Enterprise Single-Sign-On for Premium Tier customers. The following providers are supported:

* Active Directory/LDAP
* ADFS
* Azure Active Directory Native
* Google Workspace
* OpenID Connect
* Okta
* PingFederate
* SAML
* Azure Active Directory

Enterprise Sign-On is available as an add-on for [Premium Tier](/documentation/cloud/premium/) customers. If you are interested in using SSO, please [contact us](/contact-us/).
15 changes: 0 additions & 15 deletions qdrant-landing/content/documentation/cloud/support.md

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ kind: Secret
metadata:
name: qdrant-api-key
namespace: the-qdrant-namespace
type: kubernetes.io/tls
type: kubernetes.io/generic
```
With this command the secret name would be `qdrant-api-key` and the key would be `api-key`.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ To learn how Hybrid Cloud works, [read the overview document](/documentation/hyb

## Prerequisites

- **Kubernetes cluster:** To create a Hybrid Cloud Environment, you need a [standard compliant](https://www.cncf.io/training/certification/software-conformance/) Kubernetes cluster. You can run this cluster in any cloud, on-premise or edge environment, with distributions that range from AWS EKS to VMWare vSphere.
- **Kubernetes cluster:** To create a Hybrid Cloud Environment, you need a [standard compliant](https://www.cncf.io/training/certification/software-conformance/) Kubernetes cluster. You can run this cluster in any cloud, on-premise or edge environment, with distributions that range from AWS EKS to VMWare vSphere. See [Deployment Platforms](/documentation/hybrid-cloud/platform-deployment-options/) for more information.
- **Storage:** For storage, you need to set up the Kubernetes cluster with a Container Storage Interface (CSI) driver that provides block storage. For vertical scaling, the CSI driver needs to support volume expansion. For backups and restores, the driver needs to support CSI snapshots and restores.

<aside role="status">Network storage systems like NFS or object storage systems such as S3 are not supported.</aside>
Expand Down Expand Up @@ -50,6 +50,78 @@ Open Containers Initiative (OCI) Helm charts:
- `registry.cloud.qdrant.io/qdrant-charts/qdrant-cluster-manager`
- `registry.cloud.qdrant.io/qdrant-charts/prometheus`

### Rate limits at `docker.io`

By default, the Qdrant database image will be fetched from Docker Hub, which is the main source of truth. Docker Hub has rate limits for anonymous users. If you have larger setups and also fetch other images from their, you may run into these limits. To solve this, you can provide authentication information for Docker Hub.

First, create a secret with your Docker Hub credentials into your `the-qdrant-namespace` namespace:

```shell
kubectl create secret docker-registry dockerhub-registry-secret --namespace the-qdrant-namespace --docker-server=https://index.docker.io/v1/ --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email>
```

Then, you can reference this secret by adding the following configuration in the operator configuration YAML editor in the advanced section of the Hybrid Cloud Environment:

```yaml
qdrant:
image:
pull_secret: "dockerhub-registry-secret"
```
### Mirroring images and charts
To mirror all necessary container images and Helm charts into your own registry, you can either use a replication feature that your registry provides, or you can manually sync the images with [Skopeo](https://github.com/containers/skopeo):
You can find your personal credentials for the Qdrant Cloud registry in the onboarding command, or you can fetch them with `kubectl`:

```shell
kubectl get secrets qdrant-registry-creds --namespace the-qdrant-namespace -o jsonpath='{.data.\.dockerconfigjson}' | base64 --decode | jq -r '.'
```

First login to the source registry:

```shell
skopeo login registry.cloud.qdrant.io
```

Then login to your own registry:

```shell
skopeo login your-registry.example.com
```

To sync all container images:

```shell
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant/qdrant-operator your-registry.example.com/qdrant/qdrant-operator
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant/qdrant-cloud-agent your-registry.example.com/qdrant/qdrant-cloud-agent
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant/prometheus your-registry.example.com/qdrant/prometheus
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant/prometheus-config-reloader your-registry.example.com/qdrant/prometheus-config-reloader
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant/kube-state-metrics your-registry.example.com/qdrant/kube-state-metrics
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant/qdrant your-registry.example.com/qdrant/qdrant
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant/cluster-manager your-registry.example.com/qdrant/cluster-manager
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant/operator your-registry.example.com/qdrant/operator
```

To sync all helm charts:

```shell
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant-charts/prometheus your-registry.example.com/qdrant-charts/prometheus
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant-charts/qdrant-operator your-registry.example.com/qdrant-charts/qdrant-operator
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant-charts/qdrant-operator-crds your-registry.example.com/qdrant-charts/qdrant-operator-crds
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant-charts/qdrant-cloud-agent your-registry.example.com/qdrant-charts/qdrant-cloud-agent
skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant-charts/operator your-registry.example.com/qdrant-charts/operator
```

With the above configuration, you can add the following values to the advanced section of your Hybrid Cloud Environment:

* Container registry URL: `your-registry.example.com/qdrant`
* Chart repository URL: `oci://your-registry.example.com/qdrant-charts`

If you registry requires authentication, you have to create your own secrets with authentication information into your `the-qdrant-namespace` namespace.

You can then reference they secret by

## Installation

1. To set up Hybrid Cloud, open the Qdrant Cloud Console at [cloud.qdrant.io](https://cloud.qdrant.io). On the dashboard, select **Hybrid Cloud**.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ weight: 5

This page provides an overview of how to deploy Qdrant Hybrid Cloud on various managed Kubernetes platforms.

For a general list of prerequisites and installation steps, see our [Hybrid Cloud setup guide](/documentation/hybrid-cloud/hybrid-cloud-setup/).
For a general list of prerequisites and installation steps, see our [Hybrid Cloud setup guide](/documentation/hybrid-cloud/hybrid-cloud-setup/). This platform specific documentation also applies to Qdrant Private Cloud.

![Akamai](/documentation/cloud/cloud-providers/akamai.jpg)

Expand Down
20 changes: 20 additions & 0 deletions qdrant-landing/content/documentation/private-cloud/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
title: Private Cloud
weight: 10
---

# Qdrant Private Cloud

Qdrant Private Cloud allows you to manage Qdrant database clusters in any Kubernetes cluster on any infrastucture. It uses the same Qdrant Operator that powers Qdrant Managed Cloud and Qdrant Hybrid Cloud, but without any connection to the Qdrant Cloud Management Console.

On top of the open source Qdrant database, it allows

* Easy deployment and management of Qdrant database clusters in your own Kubernetes infrastructure
* Zero-downtime upgrades of the Qdrant database with replication
* Vertical and horizontal up and downscaling of the Qdrant database with auto rebalancing and shard splitting
* Full control over scheduling, including Multi-AZ deployments
* Backup & Disaster Recovery
* Extended telemetry
* Qdrant Enterprise Support Services

If you are interested in using Qdrant Private Cloud, please [contact us](/contact-us/) for more information.
Loading

0 comments on commit 6dca56c

Please sign in to comment.