Merge pull request #1615 from qdrant/feat/bashofmann/cloud-design-refresh

Update cloud docs after design refresh
2026-09-27 23:18:29 +02:00 · 2025-05-02 18:40:56 +02:00
parent cd056f79d9 4684dc5c3c
commit 7e87283b1d
67 changed files with 104 additions and 86 deletions
@@ -1,7 +1,9 @@
 ---
 title: Account Setup
-weight: 10
+weight: 13
+partition: cloud
 aliases:
+  - /documentation/cloud/qdrant-cloud-setup/
 ---

 # Setting up a Qdrant Cloud Account
@@ -23,7 +25,7 @@ Every account is tied to an email address. You can invite additional users to yo

 ## Inviting additional users to an account

-You can invite additional users to your account, and manage their permissions on the *Account Management* page in the Qdrant Cloud Console.
+You can invite additional users to your account, and manage their permissions on the **Account -> Access Management** page in the Qdrant Cloud Console.

 ![Invitations](/documentation/cloud/invitations.png)

@@ -37,9 +39,15 @@ If you have access to multiple accounts, you can switch between accounts with th

 ![Switching between accounts](/documentation/cloud/account-switcher.png)

+## Light & Dark Mode
+
+The Qdrant Cloud Console supports light and dark mode. You can switch between the two modes in the *Settings* menu, by clicking on your account picture in the top right corner.
+
+![Light & Dark Mode](/documentation/cloud/light-dark-mode.png)
+
 ## Account settings

-You can configure your account settings in the Qdrant Cloud Console, by clicking on your account picture in the top right corner, and selecting *Profile*.
+You can configure your account settings in the Qdrant Cloud Console on the **Account -> Settings** page.

 The following functionality is available.

@@ -53,6 +61,9 @@ If you use multiple accounts for different purposes, it is a good idea to give t

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

+![Delete Account](/documentation/cloud/account-delete.png)
+
+
 ## Enterprise Single-Sign-On (SSO)

 Qdrant Cloud supports Enterprise Single-Sign-On for Premium Tier customers. The following providers are supported:
@@ -2,6 +2,8 @@
 title: Qdrant Cloud API
 weight: 27
 partition: cloud
+aliases:
+  - /documentation/qdrant-cloud-api/
 ---
 # Qdrant Cloud API

@@ -1,6 +1,9 @@
 ---
 title: Getting Started
-weight: 1
+weight: 12
+partition: cloud
+aliases:
+  - /documentation/cloud/getting-started/
 ---

 # Getting Started with Qdrant Managed Cloud
@@ -26,7 +29,3 @@ After setting up your account, you can create a Qdrant Cluster by following the
 For a production-ready environment, consider deploying a multi-node Qdrant cluster (at least three nodes) with replication enabled. Instructions for configuring distributed clusters are available in the [Distributed Deployment](/documentation/guides/distributed_deployment/) guide.

 If you are looking to optimize costs, you can reduce memory usage through [Quantization](/documentation/guides/quantization/) or by [offloading vectors to disk](/documentation/concepts/storage/#configuring-memmap-storage).
-
-## Support
-
-If you need assistance, you can reach our Support Team through the Qdrant Cloud UI or directly via [https://support.qdrant.io/](https://support.qdrant.io/). Information on service-level agreements is provided at [https://qdrant.to/sla](https://qdrant.to/sla).
@@ -1,6 +1,9 @@
 ---
 title: Premium Tier
-weight: 66
+weight: 19
+partition: cloud
+aliases:
+  - /documentation/cloud/premium/
 ---

 # Qdrant Cloud Premium Tier
@@ -1,10 +1,12 @@
 ---
 title: Billing & Payments
-weight: 65
+weight: 18
+partition: cloud
 aliases:
  - aws-marketplace
  - gcp-marketplace
  - azure-marketplace
+  - /documentation/cloud/pricing-payments/
 ---

 # Qdrant Cloud Billing & Payments
@@ -7,6 +7,7 @@ aliases:
  - cloud-quick-start
  - cloud-quickstart
  - cloud/quickstart-cloud/
+  - /documentation/quickstart-cloud/
 ---
 # How to Get Started With Qdrant Cloud

@@ -14,20 +15,22 @@ aliases:
 <p style="text-align: center;">You can try vector search on Qdrant Cloud in three steps. 
 </br> Instructions are below, but the video is faster:</p>

-## Setup a Qdrant Cloud cluster
+## Setup a Qdrant Cloud Cluster

 1. Register for a [Cloud account](https://cloud.qdrant.io/signup) with your email, Google or Github credentials.
-2. Go to **Overview** and follow the onboarding instructions under **Create First Cluster**. 
+2. Go to **Clusters** and follow the onboarding instructions under **Create First Cluster**. 

 ![create a cluster](/docs/gettingstarted/gui-quickstart/create-cluster.png)

-3. When you create it, you will receive an API key. You will need to copy and paste it soon.
-4. Your new cluster will be created under **Clusters**. Give it a few moments to provision.
+3. When you create it, you will receive an API key. You will need to copy it and store it somewhere self. It will not be displayed again. If you loose it, you can always create a new one on the **Cluster Detail Page** later.

-## Access the cluster dashboard
+![get api key](/docs/gettingstarted/gui-quickstart/api-key.png)

-1. Go to your **Clusters**. Under **Actions**, open the **Dashboard**.
-2. Paste your new API key here. You can revoke and create new API keys in **Access Management**.
+
+## Access the Cluster UI
+
+1. Click on **Cluster UI** on the **Cluster Detail Page** to access the cluster UI dashboard.
+2. Paste your new API key here. You can revoke and create new API keys in the **API Keys** tab on your **Cluster Detail Page**.
 3. The key will grant you access to your Qdrant instance. Now you can see the cluster Dashboard.

 ![access the dashboard](/docs/gettingstarted/gui-quickstart/access-dashboard.png)
@@ -108,7 +111,7 @@ client, err := qdrant.NewClient(&qdrant.Config{
 })
 ```

-## Try the Tutorial sandbox
+## Try the Tutorial Sandbox

 1. Open the interactive **Tutorial**. Here, you can test basic Qdrant API requests.
 2. Using the **Quickstart** instructions, create a collection, add vectors and run a search.
@@ -116,11 +119,11 @@ client, err := qdrant.NewClient(&qdrant.Config{

 ![interactive-tutorial](/docs/gettingstarted/gui-quickstart/interactive-tutorial.png)

-## That's vector search!
+## That's Vector Search!
 You can stay in the sandbox and continue trying our different API calls.</br>
 When ready, use the Console and our complete REST API to try other operations.

-## What's next?
+## What's Next?

 Now that you have a Qdrant Cloud cluster up and running, you should [test remote access](/documentation/cloud/authentication/#test-cluster-access) with a Qdrant Client.

@@ -1,6 +1,6 @@
 ---
 title: Cloud RBAC
-weight: 16
+weight: 14
 partition: cloud
 ---

@@ -5,14 +5,10 @@ weight: 1

 # Role Management

-
-
 > 💡 You can access this in **Access Management > User & Role Management** *if available see [this page for details](/documentation/cloud-rbac/).*

-
 A **Role** contains a set of **permissions** that define the ability to perform or control specific actions in Qdrant Cloud. Permissions are accessible through the Permissions tab in the Role Details page and offer fine-grained access control, logically grouped for easy identification.

-
 ## Built-In Roles

 Qdrant Cloud includes some built-in roles for common use-cases. The permissions for these built-in roles cannot be changed.
@@ -29,7 +25,7 @@ There are three types:

 An authorized user can create their own custom roles with specific sets of permissions, giving them more control over who has what access to which resource.

-![image.png](/documentation/cloud/role-based-access-control/custom-roles.png)
+![image.png]( /documentation/cloud/role-based-access-control/custom-roles.png)

 ### Creating a Custom Role

@@ -42,8 +38,6 @@ Once created, the new role will appear under the **Custom Roles** section in the

 ![image.png](/documentation/cloud/role-based-access-control/create-custom-role.png)

-![image.png](/documentation/cloud/role-based-access-control/create-new-role.png)
-
 ### Editing a Custom Role

 To update a specific role's permissions, select it from the list and click on the **Permissions** tab. Here, you'll find logically grouped options that are easy to identify and edit as needed. Once you've made your changes, save them to apply the updated permissions to the role.
@@ -3,27 +3,16 @@ title: User Management
 weight: 2
 ---

-
 # User Management

-
-
 > 💡 You can access this in **Access Management > User & Role Management** *if available see [this page for details](/documentation/cloud-rbac/).*

-
-
-
 ## Inviting Users to an Account

-
 Users can be invited via the **User Management** section, where they are assigned the **Base role** by default. Additionally, users have the option to select a specific role when inviting another user. The **Base role** is a predefined role with minimal permissions, granting users access to the platform while restricting them to viewing only their own profile.

 ![image.png](/documentation/cloud/role-based-access-control/user-invitation.png)

-
-
-
-
 ### Inviting Users from a Role

 Users can be invited attached to a specific role by inviting them through the **Role Details** page - just click on the Users tab and follow the prompts.
@@ -20,8 +20,8 @@ content:
    - id: 1
      image:
        src: /img/dev-portal-cloud/managed-cloud.png
-        alt: Qdrant Cloud
-      title: Qdrant Cloud
+        alt: Managed Cloud
+      title: Managed Cloud
      description: Qdrant Managed Cloud is our SaaS solution, providing managed Qdrant database clusters on the cloud.
      link:
        url: /documentation/cloud/
@@ -1,6 +1,6 @@
 ---
 title: Managed Cloud
-weight: 12
+weight: 15
 aliases:
  - /documentation/overview/qdrant-alternatives/documentation/cloud/
 partition: cloud
@@ -14,7 +14,7 @@ Transitioning to the Managed Cloud version of Qdrant does not change how you int

 You can also attach your own infrastructure as a Hybrid Cloud Environment. For details, see our [Hybrid Cloud](/documentation/hybrid-cloud/) documentation.

-## Cluster configuration
+## Cluster Configuration

 Each database cluster comes pre-configured with the following tools, features, and support services:

@@ -26,4 +26,3 @@ Each database cluster comes pre-configured with the following tools, features, a
 - Available natively on AWS and GCP, and Azure. 
 - Available on your own infrastructure and other providers if you use the Hybrid Cloud.

-## Ready? [**Click here to get started!**](/documentation/cloud/getting-started/)
@@ -11,26 +11,30 @@ Database API keys can be configured with granular access control. Database API k

 Database API keys with granular access control are available for clusters using version **v1.11.0** and above.

-## Create Database API keys
+## Create Database API Keys

 <aside role="alert">
    The API key is only shown once after creation. If you lose it, you will need to create a new one. 
 </aside>

+![API Key](/documentation/cloud/create-api-key.png)
+
 1. Go to the [Cloud Dashboard](https://qdrant.to/cloud).
-2. Go to the **API Keys** section of the Cluster detail page.
+2. Go to the **API Keys** section of the **Cluster Detail Page**.
 3. Click **Create**.
 4. Choose a name and an optional expiration (in days, the default is 90 days) for your API key. An empty expiration will result in no expiration.
 5. By default, tokens are given cluster-wide permissions, with a choice between manage/write permissions (default) or read-only.<br/><br/>To restrict a token to a subset of collections, you can select the Collections tab and choose from the collections available in your cluster.
 6. Click **Create** and retrieve your API key.

+![API Key](/documentation/cloud/api-key.png)
+
 We recommend configuring an expiration and rotating your API keys regularly as a security best practice.

 <iframe width="560" height="315" src="https://www.youtube.com/embed/3c-8tcBIVdQ?si=OoyobgPTU-DHIhee" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

-## Admin Database API keys
+## Admin Database API Keys

-The previous iteration of Database API keys, called Admin Database API keys, do not have granular access control. Clusters created before January 27, 2025 will still see the option to create Admin Database API keys. Older Admin Database API keys will continue to work but we do recommend switching to Database API keys with granular access control to take advantage of better security controls.
+The previous iteration of Database API keys, called Admin Database API keys, do not have granular access control. Clusters created before January 27, 2025 will still see the option to create Admin Database API keys. Older Admin Database API keys will continue to work, but we do recommend switching to Database API keys with granular access control to take advantage of better security controls.

 <aside role="alert">
    Enabling Database API keys with granular access control will trigger a restart of your cluster.
@@ -40,7 +44,7 @@ To enable Database API keys with granular access control, click **Enable** on th

 After enabling Database API keys with granular access control for a cluster, existing Admin Database API keys will continue to work, but you will not be able to create new Admin Database API Keys.

-## Test cluster access
+## Test Cluster Access

 After creation, you will receive a code snippet to access your cluster. Your generated request should look very similar to this one:

@@ -27,7 +27,7 @@ set up your cluster, as described in the following sections:
 - Set up [Authentication](/documentation/cloud/authentication/)
 - Configure one or more [Collections](/documentation/concepts/collections/)

-## Automatic backups
+## Automatic Backups

 You can set up automatic backups of your clusters with our Cloud UI. With the
 procedures listed in this page, you can set up
@@ -44,16 +44,12 @@ need. You can restore a cluster from the snapshot of your choice.
 >   - Node count
 >   - Qdrant version

-### Configure a backup
+### Configure a Backup

 After you have taken the prerequisite steps, you can configure a backup with the
 [Qdrant Cloud Dashboard](https://cloud.qdrant.io). To do so, take these steps:

-1. Sign in to the dashboard
-1. Select Clusters.
-1. Select the cluster that you want to back up.
-   ![Select a cluster](/documentation/cloud/select-cluster.png)
-1. Find and select the **Backups** tab.
+1. On the **Cluster Detail Page** and select the **Backups** tab.
 1. Now you can set up a backup schedule.
   The **Days of Retention** is the number of days after a backup snapshot is
   deleted.
@@ -61,7 +57,7 @@ After you have taken the prerequisite steps, you can configure a backup with the

 ![Configure a cluster backup](/documentation/cloud/backup-schedule.png)

-### Restore a backup
+### Restore a Backup

 If you have a backup, it appears in the list of **Available Backups**. You can
 choose to restore or delete the backups of your choice.
@@ -70,7 +66,7 @@ choose to restore or delete the backups of your choice.

 <!-- I think we should move this to the Snapshot page, but I'll do it later -->

-## Backups with a snapshot
+## Backups With a Snapshot

 Qdrant also offers a snapshot API which allows you to create a snapshot
 of a specific collection or your entire cluster. For more information, see our
@@ -88,7 +84,7 @@ Here is how you can take a snapshot and recover a collection:
 3. Recover the snapshot:
   - Call the [recover endpoint](/documentation/concepts/snapshots/#recover-in-cluster-deployment). Set a location which points to the snapshot file (`file:///qdrant/snapshots/{collection_name}/{snapshot_file_name}`) for each host.

-## Backup considerations
+## Backup Considerations

 Backups are incremental for AWS and GCP clusters. For example, if you have two backups, backup number 2
 contains only the data that changed since backup number 1. This reduces the
@@ -5,13 +5,17 @@ weight: 35

 # Accessing Qdrant Cloud Clusters

-Once you [created](/documentation/cloud/create-cluster/) a cluster, and set up an [API key](/documentation/cloud/authentication/), you can access your cluster through the integrated Web UI, the REST API and the GRPC API.
+Once you [created](/documentation/cloud/create-cluster/) a cluster, and set up an [API key](/documentation/cloud/authentication/), you can access your cluster through the integrated Cluster UI, the REST API and the GRPC API.

-## Web UI
+## Cluster UI

-There is the convenient link on the cluster detail page in the Qdrant Cloud Console to access the [Web UI](/documentation/web-ui/) of your cluster.
+There is the convenient link on the cluster detail page in the Qdrant Cloud Console to access the [Cluster UI](/documentation/web-ui/).

-![Cluster Web UI](/documentation/cloud/cloud-db-dashboard.png)
+![Cluster Cluster UI](/documentation/cloud/cloud-db-dashboard.png)
+
+The Overview tab also contains direct links to explore Qdrant tutorials and sample datasets.
+
+![Cluster Cluster UI Tutorials](/documentation/cloud/cloud-db-deeplinks.png)

 ## API

@@ -21,7 +25,7 @@ The REST API is exposed on your cluster endpoint at port `6333`. The GRPC API is

 Have a look at the [API reference](/documentation/interfaces/#api-reference) and the official [client libraries](/documentation/interfaces/#client-libraries)  for more information on how to interact with the Qdrant Cloud API.

-## Node specific endpoints
+## Node Specific Endpoints

 Next to the cluster endpoint which loadbalances requests across all healthy Qdrant nodes, each node in the cluster has its own endpoint as well. This is mainly usefull for monitoring or manual shard management purpuses.

@@ -7,23 +7,27 @@ weight: 55

 ## Telemetry

+![Cluster Metrics](/documentation/cloud/cluster-metrics.png)
+
 Qdrant Cloud provides you with a set of metrics to monitor the health of your database cluster. You can access these metrics in the Qdrant Cloud Console in the **Metrics** and **Request** sections of the cluster details page.

 ## Logs

+![Cluster Logs](/documentation/cloud/cluster-logs.png)
+
 Logs of the database cluster are available in the Qdrant Cloud Console in the **Logs** section of the cluster details page.

 ## Alerts

 You will receive automatic alerts via email before your cluster reaches the currently configured memory or storage limits, including recommendations for scaling your cluster.

-## Qdrant database metrics and telemetry
+## Qdrant Database Metrics and Telemetry

 You can also directly access the metrics and telemetry that the Qdrant database nodes provide.

 To scrape metrics from a Qdrant cluster running in Qdrant Cloud, an [API key](/documentation/cloud/authentication/) is required to access `/metrics` and `/sys_metrics`. Qdrant Cloud also supports supplying the API key as a [Bearer token](https://www.rfc-editor.org/rfc/rfc6750.html), which may be required by some providers.

-### Qdrant Node metrics
+### Qdrant Node Metrics

 Metrics in a Prometheus compatible format are available at the `/metrics` endpoint of each Qdrant database node. When scraping, you should use the [node specific URLs](/documentation/cloud/cluster-access/#node-specific-endpoints) to ensure that you are scraping metrics from all nodes in each cluster. For more information see [Qdrant monitoring](/documentation/guides/monitoring/).

@@ -31,13 +35,13 @@ You can also access the `/telemetry` [endpoint](https://api.qdrant.tech/api-refe

 For more information, see [Qdrant monitoring](/documentation/guides/monitoring/).

-### Cluster system metrics
+### Cluster System Metrics

 Cluster system metrics is a cloud-only endpoint that not only shares all the information about the database from `/metrics` but also provides additional operational data from our infrastructure about your cluster, including information from our load balancers, ingresses, and cluster workloads themselves.

 Metrics in a Prometheus-compatible format are available at the `/sys_metrics` cluster endpoint. Database API Keys are used to authenticate access to cluster system metrics. `/sys_metrics` only need to be queried once per cluster on the main load-balanced cluster endpoint. You don't need to scrape each cluster node individually, instead it will always provide metrics about all nodes.

-## Grafana dashboard
+## Grafana Dashboard

 If you scrape your Qdrant Cluster system metrics into your own monitoring system, and your are using Grafana, you can use our [Grafana dashboard](https://github.com/qdrant/qdrant-cloud-grafana-dashboard) to visualize these metrics.

@@ -45,7 +49,7 @@ If you scrape your Qdrant Cluster system metrics into your own monitoring system

 <iframe width="560" height="315" src="https://www.youtube.com/embed/pKPP-tL5_6w?si=ASKiG1P61m2YYk9J" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

-### Cluster system metrics `/sys_metrics`
+### Cluster System Mtrics `/sys_metrics`

 In Qdrant Cloud, each Qdrant cluster will expose the following metrics. This endpoint is not available when running Qdrant open-source.

@@ -11,7 +11,7 @@ The amount of data is always growing and at some point you might need to upgrade

 There are different options for how it can be done.

-## Vertical scaling
+## Vertical Scaling

 Vertical scaling is the process of increasing the capacity of a cluster by adding or removing CPU, storage and memory resources on each database node.

@@ -21,7 +21,7 @@ If you want to scale your cluster down, the new, smaller memory size must be sti

 Note, that it is not possible to scale down the disk space of the cluster due to technical limitations of the underlying cloud providers.

-## Horizontal scaling
+## Horizontal Scaling

 Vertical scaling can be an effective way to improve the performance of a cluster and extend the capacity, but it has some limitations. The main disadvantage of vertical scaling is that there are limits to how much a cluster can be expanded. At some point, adding more resources to a cluster can become impractical or cost-prohibitive.

@@ -1,16 +1,16 @@
 ---
-title: Upgrade Clusters
+title: Update Clusters
 weight: 55
 ---

-# Upgrading Qdrant Cloud Clusters
+# Updating Qdrant Cloud Clusters

-As soon as a new Qdrant version is available. Qdrant Cloud will show you an upgrade notification in the Cluster list and on the Cluster details page.
+As soon as a new Qdrant version is available. Qdrant Cloud will show you an update notification in the Cluster list and on the Cluster details page.

-To upgrade to a new version, go to the Cluster details page, choose the new version from the version dropdown and click **Upgrade**.
+To update to a new version, go to the Cluster details page, choose the new version from the version dropdown and click **Update**.

-![Cluster Upgrades](/documentation/cloud/cluster-upgrades.png)
+![Cluster Updates](/documentation/cloud/cluster-upgrades.png)

-If you have a multi-node cluster and if your collections have a replication factor of at least **2**, the upgrade process will be zero-downtime and done in a rolling fashion. You will be able to use your database cluster normally. 
+If you have a multi-node cluster and if your collections have a replication factor of at least **2**, the update process will be zero-downtime and done in a rolling fashion. You will be able to use your database cluster normally. 

-If you have a single-node cluster or a collection with a replication factor of **1**, the upgrade process will require a short downtime period to restart your cluster with the new version.
+If you have a single-node cluster or a collection with a replication factor of **1**, the update process will require a short downtime period to restart your cluster with the new version.
@@ -54,7 +54,9 @@ You have a broad choice of regions on AWS, Azure and Google Cloud.

 For payment information see [**Pricing and Payments**](/documentation/cloud/pricing-payments/).

-## Create a cluster
+## Create a Cluster
+
+![Create Cluster Page](/documentation/cloud/create-cluster.png)

 This page shows you how to use the Qdrant Cloud Console to create a custom Qdrant Cloud cluster.

@@ -85,15 +87,17 @@ This page shows you how to use the Qdrant Cloud Console to create a custom Qdran

 Once provisioned, you can access your cluster on ports 443 and 6333 (REST) and 6334 (gRPC).

-![Cluster configured in the UI](/docs/cloud/create-cluster-test.png)
+![Cluster configured in the UI](/documentation/cloud/cluster-detail.png)

 You should now see the new cluster in the **Clusters** menu.

-## Deleting a cluster
+## Deleting a Cluster

 You can delete a Qdrant database cluster from the cluster's detail page.

-## Next steps
+![Delete Cluster](/documentation/cloud/delete-cluster.png)
+
+## Next Steps

 You will need to connect to your new Qdrant Cloud cluster. Follow [**Authentication**](/documentation/cloud/authentication/) to create one or more API keys. 

@@ -1,6 +1,6 @@
 ---
 title: Hybrid Cloud
-weight: 13
+weight: 16
 partition: cloud
 ---

@@ -24,7 +24,7 @@ These settings can also be changed after the cluster is created on the cluster d

 When creating or editing a cluster, you can configure how the database Pods get scheduled in your Kubernetes cluster. This can be useful to ensure that the Qdrant databases will run on dedicated nodes. You can configure the necessary node selectors and tolerations in the "Kubernetes Configuration" section during cluster creation, or on the cluster detail page.

-### Authentication to your Qdrant clusters
+### Authentication to your Qdrant Clusters

 <aside role="alert">By default, clusters in Hybrid Cloud are only exposed through a Kubernetes ClusterIP Service inside of the Kubernetes network and not accessible to the outside, and no API key is configured. If you choose to expose the database internally or externally, you must configure an API key.</aside>

@@ -32,7 +32,7 @@ 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.

-![Hybrid Cloud cluster configuration](/documentation/cloud/hybrid_cloud_detail_cluster_configuration.png)
+![Hybrid Cloud API Key configuration](/documentation/cloud/hybrid_cloud_api_key.png)

 One way to create a secret is with kubectl:

@@ -89,6 +89,8 @@ 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.

+![Hybrid Cloud API Key configuration](/documentation/cloud/hybrid_cloud_service.png)
+
 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:
@@ -157,6 +159,8 @@ If you want to offload TLS at the ingress or loadbancer level, please refer to t

 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.

+![Hybrid Cloud API Key configuration](/documentation/cloud/hybrid_cloud_tls.png)
+
 To create such a secret, you can use `kubectl`:

 ```shell
@@ -1,6 +1,6 @@
 ---
 title: Private Cloud
-weight: 14
+weight: 17
 partition: cloud
 ---