Skip to content
Stackship documentation Svenska

Vector stores (Qdrant)Users

Create a vector store

Create a Qdrant vector store in a resource group, choose its size and replicas, and decide whether it is served over HTTPS.

Requires: qdrantcluster/write

Creating a vector store needs qdrantcluster/write in the resource group; the Owner, Contributor and Databases Operator roles have it.

Open the wizard

In the portal at https://portal.example.com, open Vector Store in the sidebar and choose Create Vector Stores. The Create Vector Store Cluster wizard has four steps: Basics, Resources, Networking and Review & Create.

Basics

  • Vector Store Cluster Name — 3 to 50 characters: lowercase letters, digits and hyphens, not starting or ending with a hyphen. It must not be taken by another vector store in the resource group, and it cannot be changed later.
  • Boundary, Cluster and Resource group — where the vector store runs. Each is filled in for you when there is only one choice.

Resources

Choose a compute plan. Each plan shows its CPU, memory, storage and number of replicas; the plans are listed in Plans and limits. Plans that a policy on the boundary does not allow are disabled, and a plan larger than your installation's nodes can host is refused when you create the vector store.

Under Advanced, Number of Replicas (1 to 5) overrides the plan's replica count. Read Replicas and sharding before you choose more than one: extra replicas add servers, but they only protect a collection that you create with a replication factor above 1.

The storage size comes from the plan. Each replica gets a volume of that size, and the size does not change when you change the plan later.

Networking

  • Enable HTTPS — on by default. The REST API and Qdrant's dashboard are served over HTTPS on a generated hostname, with a certificate issued for it. This is the only way to reach the dashboard. Turn it off to keep the vector store reachable only inside the Kubernetes cluster.
  • Custom domain — optional, shown while HTTPS is on. Leave it empty to use the generated hostname, which is built from the boundary, the resource group and the vector store's name, under your installation's Qdrant domain. A custom domain is a lowercase domain name such as vectors.example.com; create a DNS record that points it at the platform's ingress before its certificate can be issued.

Access over a load balancer, and a list of allowed networks, are set after creation — see Networking and the API key.

Review and create

Review & Create shows the name, resource group, Version, API Key Auth, the resources, HTTPS and Domain, and the number of replicas. Every vector store is created with Qdrant v1.13.2 and with API key authentication on; you can change the version afterwards in Runtime.

Choose Submit. The vector store appears in the list as Creating and turns Running when all its servers are ready; see Statuses. Creating is refused when:

  • HTTPS is on and your installation has no certificate issuer for it — turn HTTPS off, or ask your platform administrator;
  • HTTPS is on without a custom domain and your installation has no Qdrant domain — enter a custom domain, or ask your platform administrator.

With the CLI

bash
stsh qdrant create my-vectors -g my-resource-group -c my-cluster \
  --set computePlan=small --set apiKeyEnabled=true --set enableIngress=true

The CLI and the API do not turn API key authentication or HTTPS on for you: without apiKeyEnabled=true the vector store has no API key. Settings you do not give come from the plan; the version defaults to v1.13.2.

Next steps