Setting Up Qdrant Hybrid Cloud

You've already chosen Hybrid Cloud (managed control plane on your own infra). If you're still deciding, that's the qdrant-deployment-options skill. Most setup failures trace to one of two things: storage (the CSI driver can't do what Qdrant needs) or connectivity (the agent can't reach Qdrant Cloud). Diagnose which before touching anything else.

Preparing the Kubernetes cluster (do this first)

Use when: about to create the environment, or the install/cluster provisioning failed on storage.

• Qdrant needs a block-storage CSI driver. Network storage (NFS) and object storage (S3) are unsupported: a cluster wired to those will fail, not degrade Prerequisites.
• Create the StorageClass (with allowVolumeExpansion: true) and the VolumeSnapshotClass beforehand, not after. Without volume expansion you can't grow disk later; without a VolumeSnapshotClass and the CSI snapshot controller you can't take backups.
• Any standards-compliant Kubernetes works, and there's platform-specific setup guidance for the managed ones: Akamai (Linode/LKE), AWS (EKS), Civo, DigitalOcean (DOKS), Gcore, GCP (GKE), Azure (AKS), Oracle (OKE), OVHcloud, Red Hat OpenShift, Scaleway, STACKIT, and Vultr Deployment Platforms.
• Platform matters for what storage supports: some (e.g. Linode/LKE, Vultr) don't support CSI volume snapshots at all, so backups are unavailable there. Check your provider's snapshot page and prefer its recommended instance and disk types (e.g. gp3 on EKS, Premium SSD v2 on AKS) before committing.
• Confirm outbound connectivity: the agent opens connections to grpc.cloud.qdrant.io and api.cloud.qdrant.io on 443. Firewalls/egress proxies block this silently: a "stuck installing" agent is usually this.
• You need cluster-admin plus kubectl and helm configured against the target cluster.

Creating the environment

Use when: running the install wizard in the Cloud Console.