Qdrant documentation

For production use cases, please pin the version of the qdrant image in the values.yaml file to a specific version instead of latest

helm repo add qdrant https://qdrant.github.io/qdrant-helm
helm repo update
helm install your-qdrant-installation-name qdrant/qdrant

This chart installs and bootstraps a Qdrant instance.

• Kubernetes
• Helm
• PV provisioner (by the infrastructure)

You can install the chart via:

helm install your-qdrant-installation-name .

To install a specific version of the qdrant image

helm install your-qdrant-installation-name . --set image.tag=v0.9.0

DISCLAIMER: This could lead to unexpected behaviour depending on chart version vs Qdrant image version

Unistall via:

helm delete your-qdrant-installation-name .

Delete the volume with

kubectl delete pvc -l kubectl delete pvc -l app.kubernetes.io/instance=your-qdrant-installation-name

For documentation of the settings please refer to Qdrant Configuration File All of these configuration options could be overwritten under config in values.yaml. A modifcation example is provided there.

Running a distributed cluster just needs a few changes in your values.yaml file. Increase the number of replicas to the desired number of nodes and set config.cluster.enabled to true.

Depending on your environment or cloud provider you might need to change the service in the values.yaml as well. For example on AWS EKS you would need to change the cluster.type to NodePort.

Disclaimer: Snapshot restoration is only supported for single qdrant node setups

To restore a snapshot create a Persistent Volume and a Persistent Volume Claim using a storage class according to your setup, copy the snapshots to the PV, enable snapshot restoration along with the snapshot file names and pvc name in values.yaml file and run the helm install command.

Example EBS pv, pvc and volume creation command is added in examples directory Note: Make sure volume is on the same region and availability zone as where qdrant is going to be installed.

To enable rolling update on config map modification set updateConfigurationOnChange to true