krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-03 01:48:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

Hybrid Cloud setup changes

Browse Source
This commit is contained in:
Abdon Pijpelink
2026-06-17 15:14:06 +02:00
parent b11f6001c9
commit f66ce549c3
7 changed files with 17 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/hybrid-cloud/hybrid-cloud-setup.md
+17 -16
View File
@@ -49,36 +49,37 @@ You will need to have access to the Kubernetes cluster with `kubectl` and `helm`
3. Now you can specify the following:
- **Name:** A name for the Hybrid Cloud Environment
- **Kubernetes Namespace:** The Kubernetes namespace for the services (like agent and operator). Once you select a namespace, you can't change it.
- **Environment Name:** A name for the Hybrid Cloud Environment
- **Kubernetes Namespace:** The Kubernetes namespace for the services (like agent and operator). Once you select a namespace, you can't change it.
You can also configure the StorageClass and VolumeSnapshotClass to use for the Qdrant databases, if you want to deviate from the default settings of your cluster.
You can also configure the StorageClass and VolumeSnapshotClass to use for the Qdrant databases, if you want to deviate from the default settings of your cluster.
By default, Qdrant Cloud will provision two volumes per Qdrant Pod: One for the data stored within Qdrant, and one for [collection snapshots](/documentation/snapshots/). By default, the same StorageClass will be used for both volumes. You can also configure a different StorageClass in the advanced configuration options of your Hybrid Cloud environment. If you want to disable the snapshot volume, you can configure `emptyDir` as a Snapshot StorageClass.
By default, Qdrant Cloud will provision two volumes per Qdrant Pod: One for the data stored within Qdrant, and one for [collection snapshots](/documentation/snapshots/). By default, the same StorageClass will be used for both volumes. You can also configure a different StorageClass in the advanced configuration options of your Hybrid Cloud environment. If you want to disable the snapshot volume, you can configure `emptyDir` as a Snapshot StorageClass.
![Create Hybrid Cloud Environment](/documentation/cloud/hybrid_cloud_env_create.png)
![Create Hybrid Cloud Environment](/documentation/cloud/hybrid_cloud_env_create.png)
4. You can then enter the YAML configuration for your Kubernetes operator. Qdrant supports a specific list of configuration options, as described in the [Qdrant Operator configuration](/documentation/hybrid-cloud/operator-configuration/) section.
5. (Optional) If you have special requirements for any of the following, activate the **Show advanced configuration** option:
- If you use a proxy to connect from your infrastructure to the Qdrant Cloud API, you can specify the proxy URL, credentials and certificates.
- Container registry URL for Qdrant services (like Agent, Operator, Cluster-manager and monitoring stack) images. The default is <https://registry.cloud.qdrant.io/qdrant/>.
- Helm chart repository URL for the Qdrant services. The default is <oci://registry.cloud.qdrant.io/qdrant-charts>.
- An optional secret with credentials to access your own container registry.
- Log level for the operator and agent.
- Node selectors and tolerations for the operator, agent, cluster-manager and monitoring stack.
- Control Plane Labels that will be added to all Kubernetes resources of the Hybrid Cloud control-plane components.
- If you use a proxy to connect from your infrastructure to the Qdrant Cloud API, you can specify the proxy URL, credentials and certificates.
![Create Hybrid Cloud Environment - Advanced Configuration](/documentation/cloud/hybrid_cloud_advanced_configuration.png)
- Container registry URL for Qdrant services (like Agent, Operator, Cluster-manager and monitoring stack) images. The default is <https://registry.cloud.qdrant.io/qdrant/>.
- Helm chart repository URL for the Qdrant services. The default is <oci://registry.cloud.qdrant.io/qdrant-charts>.
- An optional secret with credentials to access your own container registry.
![Create Hybrid Cloud Environment - Custom Registries](/documentation/cloud/Hcloud_connection_custom_registries.png)
- Log level for the operator and agent.
- Node selectors and tolerations for the operator, agent, cluster-manager and monitoring stack.
- Control Plane Labels that will be added to all Kubernetes resources of the Hybrid Cloud control-plane components.
![Create Hybrid Cloud Environment - Connection Scheduling](/documentation/cloud/Hcloud_connection_scheduling_2.png)
![Create Hybrid Cloud Environment - Advanced Configuration](/documentation/cloud/hybrid_cloud_advanced_configuration.png)
6. Once complete, click **Create**.
6. Once complete, click the **Save and Generate Installation Command** button to proceed
> **Note:** All settings but the Kubernetes namespace can be changed later.
### Generate Installation Command
After creating your Hybrid Cloud, select **Generate Installation Command** to generate a script that you can run in your Kubernetes cluster which will perform the initial installation of the Kubernetes operator and agent.
After setting up your Hybrid Cloud, select **Save and Generate Installation Command** to generate a script that you can run in your Kubernetes cluster which will perform the initial installation of the Kubernetes operator and agent.
![Rotate Hybrid Cloud Secrets](/documentation/cloud/hybrid_cloud_create_command.png)