kubeblocks-addon-qdrant

Route legacy Qdrant provisioning requests to the primary KubeBlocks engine entry.

3|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-addon-qdrant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubeblocks-addon-qdrant
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-addon-qdrant
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-addon-qdrant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy compatibility shim for Qdrant provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-qdrant. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Core Features & Use Cases

  • Backwards-compatible provisioning path for Qdrant on KubeBlocks.
  • Maintains the legacy workflow while pointing to the primary engine entry for new tasks.
  • Useful for agents referencing older APIs or documentation, ensuring a smooth transition to the main path.

Quick Start

Refer to the primary entry kubeblocks-engine-qdrant for the recommended path and use this skill only for legacy references.

Frequently Asked Questions about kubeblocks-addon-qdrant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision Qdrant on Kubernetes using KubeBlocks legacy workflows?▼

Provision Qdrant on Kubernetes by using this legacy compatibility shim for KubeBlocks, which maintains older create-time workflows while routing new tasks to the primary engine entry point.

What is the recommended path for Qdrant provisioning on KubeBlocks?▼

The recommended provisioning path for Qdrant on KubeBlocks is the kubeblocks-engine-qdrant skill, which serves as the primary create-time entry point for new provisioning tasks.

When should I use the legacy Qdrant addon instead of the primary engine entry?▼

Use the legacy Qdrant addon when maintaining backward compatibility with older APIs or documentation references, ensuring a smooth transition to the primary KubeBlocks engine entry.

Does KubeBlocks support backward-compatible Qdrant provisioning for older agents?▼

KubeBlocks supports backward-compatible Qdrant provisioning by keeping this legacy addon callable for older references, while restricting new-path usage to the primary engine entry.

Can I use the kubeblocks-addon-qdrant skill for new cold-start agent provisioning?▼

This skill is not recommended for new cold-start agent provisioning. It serves as a legacy shim and routes create-time tasks to the kubeblocks-engine-qdrant primary entry when appropriate.

Why does KubeBlocks maintain a legacy Qdrant addon alongside the primary engine?▼

KubeBlocks maintains the legacy Qdrant addon to preserve backward compatibility for older workflow references, allowing agents to transition smoothly to the primary engine entry point.