Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / Qdrant on AKS

Qdrant on AKS — Support & Quick Start

Qdrant on AKS — Qdrant packaged as a Kubernetes application for AKS: the open-source vector database and similarity-search engine for retrieval-augmented generation (RAG) and semantic search, on your own cluster. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in yo…

Email support Product page Azure Marketplace listing

At a glance

Application portscluster-internal ClusterIP service: 6333 (REST API), 6334 (gRPC); the API has NO authentication by default — keep it cluster-internal or front it with an authenticating gateway
Service(s)StatefulSet <release>-0 in your namespace; persistence enabled by default (one PVC per pod)
Logskubectl logs -n <namespace> <release>-0
VersionQdrant 1.18.2 (Helm chart 0.1.0)
PlatformAKS (Kubernetes)

Quick start

  1. Open the offer in the Azure Marketplace and select Get It Now → Create.
  2. Pick your AKS cluster (managed identity enabled) or create a new one, and choose a namespace.
  3. Review + create: the portal installs the Helm-based application onto your cluster.
  4. Verify with `kubectl get pods -n <namespace>` (the <release>-0 pod becomes Ready) and connect your applications to the cluster-internal REST/gRPC endpoints (see First login below).

First login

  1. No credential is generated: the Qdrant API is unauthenticated inside the cluster (ClusterIP). Reach it from your workloads at http://<release>.<namespace>.svc.cluster.local:6333 (REST) or :6334 (gRPC).
  2. Health: `kubectl exec -n <namespace> <release>-0 -- wget -qO- http://127.0.0.1:6333/readyz`.
  3. Before exposing it beyond the cluster, put an authenticating gateway (or Qdrant API key configuration) in front — never publish the bare service.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, cluster region, and the output of kubectl get pods -n <namespace> and kubectl describe pod <pod> when reporting an issue.