diff --git a/qdrant-landing/content/documentation/hybrid-cloud/hybrid-cloud-setup.md b/qdrant-landing/content/documentation/hybrid-cloud/hybrid-cloud-setup.md index 421196d87..5c044ae36 100644 --- a/qdrant-landing/content/documentation/hybrid-cloud/hybrid-cloud-setup.md +++ b/qdrant-landing/content/documentation/hybrid-cloud/hybrid-cloud-setup.md @@ -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 . -- Helm chart repository URL for the Qdrant services. The default is . -- 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 . + - Helm chart repository URL for the Qdrant services. The default is . + - 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) diff --git a/qdrant-landing/static/documentation/cloud/Hcloud_connection_custom_registries.png b/qdrant-landing/static/documentation/cloud/Hcloud_connection_custom_registries.png new file mode 100644 index 000000000..5dc14120c Binary files /dev/null and b/qdrant-landing/static/documentation/cloud/Hcloud_connection_custom_registries.png differ diff --git a/qdrant-landing/static/documentation/cloud/Hcloud_connection_scheduling_2.png b/qdrant-landing/static/documentation/cloud/Hcloud_connection_scheduling_2.png new file mode 100644 index 000000000..4a6fce0f8 Binary files /dev/null and b/qdrant-landing/static/documentation/cloud/Hcloud_connection_scheduling_2.png differ diff --git a/qdrant-landing/static/documentation/cloud/hybrid_cloud_advanced_configuration.png b/qdrant-landing/static/documentation/cloud/hybrid_cloud_advanced_configuration.png index 516bb381a..3c06d715d 100644 Binary files a/qdrant-landing/static/documentation/cloud/hybrid_cloud_advanced_configuration.png and b/qdrant-landing/static/documentation/cloud/hybrid_cloud_advanced_configuration.png differ diff --git a/qdrant-landing/static/documentation/cloud/hybrid_cloud_create_cluster.png b/qdrant-landing/static/documentation/cloud/hybrid_cloud_create_cluster.png index cb175a7d1..7b9e2ff42 100644 Binary files a/qdrant-landing/static/documentation/cloud/hybrid_cloud_create_cluster.png and b/qdrant-landing/static/documentation/cloud/hybrid_cloud_create_cluster.png differ diff --git a/qdrant-landing/static/documentation/cloud/hybrid_cloud_env_create.png b/qdrant-landing/static/documentation/cloud/hybrid_cloud_env_create.png index 5bf4d47a8..46783cb11 100644 Binary files a/qdrant-landing/static/documentation/cloud/hybrid_cloud_env_create.png and b/qdrant-landing/static/documentation/cloud/hybrid_cloud_env_create.png differ diff --git a/qdrant-landing/static/documentation/cloud/hybrid_cloud_kubernetes_configuration.png b/qdrant-landing/static/documentation/cloud/hybrid_cloud_kubernetes_configuration.png index f46417b5a..1844f3e0f 100644 Binary files a/qdrant-landing/static/documentation/cloud/hybrid_cloud_kubernetes_configuration.png and b/qdrant-landing/static/documentation/cloud/hybrid_cloud_kubernetes_configuration.png differ